3 ms·
Isn’t conformance to a standard API arguably less necessary now that LLMs can read API docs and adapt? For me, the win is the expectation that sites _have_ an A
by timwis 1y ago
Isn’t conformance to a standard API arguably less necessary now that LLMs can read API docs and adapt? For me, the win is the expectation that sites _have_ an API, whether it conforms to the MCP spec or not.
- bilbo0s 1y ago-API documentation may have been poorly written. -Even with good documentation, the LLM may generate incorrect code to interact with API. (If you fix the generated code and just have the LLM call that code to interact with the API, then you're on your way to an intermediary in any case. You're basically building an "MCP-like" server.) -Security or resource allocation issues when giving LLMs direct access to APIs. (LLM has limited knowledge of when API was last called. It could call too often and, if each call is expensive, generate surprise infrastructure bills.) -So on and so forth. Lots of other potential pain points solved by having something intermediate. Should that "something" be MCP? Reasonable people can disagree on that. Works well enough right now to get done what people need done I suppose.
- what 1y agoDon’t all of these arguments apply to MCP as well?