the issue is that the MCP couples two things: tool discovery (an LLM friendly description of what tools are available and how to invoke them), and tool implementation. but "implementation" both takes effort, and doesn't need new standards. so why not focus only on discovery?
Imagine you need to connect to hundreds of tools in a single agent. MCP's goal is to drastically reduce the effort of this goal.
Most of MCP is about discovery and basic principles for tool implementation. MCP's value is that all tools are exposed in a very similar manner. This was not standardized before.
yes, but this can be achieved also if i provide a json schema for describing tools and point to files containing such descriptions, with the implementations being done externally to the protocol. what's the benefit of coupling in the implementation?
The implementation is not coupled. What is standardized is how to connect to the implemenation.