>Instead of serving 200 standalone tools, we serve three meta‑tools and let the LLM discover endpoints at run‑time.

>list_api_endpoints lets the model search the catalog (“what can I do with counterparties?”)

>get_api_endpoint_schema pulls the JSON‑schema for any route it finds

>invoke_api_endpoint executes that route with user‑supplied params

>This approach allows the LLM to dynamically discover, learn about, and invoke endpoints as needed, without requiring the entire API schema to be loaded into its context window at once. The LLM will use these tools together to search for, look up, and call endpoints on demand.

Congratulation, you have reinvented Microsoft COM, IUnknown, OLE, IDispatch, and ActiveX for LLMS!

I'm not being sarcastic or criticizing, it's actually a good idea! Just not new.

https://news.ycombinator.com/item?id=12975257

https://news.ycombinator.com/item?id=20266627

https://news.ycombinator.com/item?id=29593432

https://news.ycombinator.com/item?id=19837817

I'm also not saying there aren't better approaches, like "NeLLM": taking the NeWS approach to LLMs, where MCP is more like "X-LLM": taking the X-Windows approach to LLMs.

Sending JSON data back and forth between a Node based orchestrator and an LLM is one thing, all well and find and traditional, but why not send and evaluate JavaScript code itself? Both Node (or even a secure Node isolate) and the LLM can generate and evaluate JavaScript quite well thank you, and it's a hell of a lot more powerful and concise and extensible that a fixed JSON protocol, for the exact same reason that NeWS is a hell of a lot more powerful and concise and extensible than the fixed X-Windows protocol.

https://news.ycombinator.com/item?id=43952748

>I agree they should learn from DLLs, gRPC, SOAP, IDL, dCOM, etc.

>But they should also learn from how NeWS was better than X-Windows because instead of a fixed protocol, it allowed you to send executable PostScript code that runs locally next to the graphics hardware and input devices, interprets efficient custom network protocols, responds to local input events instantly, implements a responsive user interface while minimizing network traffic.

>For the same reason the client-side Google Maps via AJAX of 20 years ago was better than the server-side Xerox PARC Map Viewer via http of 32 years ago.

>I felt compelled to write "The X-Windows Disaster" comparing X-Windows and NeWS, and I would hate if 37 years from now, when MCP is as old as X11, I had to write about "The MCP-Token-Windows Disaster", comparing it to a more efficient, elegant, underdog solution that got out worse-is-bettered. It doesn't have to be that way!

>The X-Windows Disaster:

https://donhopkins.medium.com/the-x-windows-disaster-128d398...

>It would be "The World's Second Fully Modular Software Disaster" if we were stuck with MCP for the next 37 years, like we still are to this day with X-Windows.