2 Comments
User's avatar
Ashish Deshpande's avatar

MCP design could be a huge field in itself. Data pull from MCP should be pointed and its use case should also be. This is a classic context engineering case where the agent gets overloaded witb context beyond its scope.

Ryan Eade's avatar

I completely agree, MCP isn't just a wrapper around your API. Most APIs weren't well designed to begin with and included way too many endpoints and were not structured around intent and actions. Many platforms have APIs that look very similar to their data model, and that's fine for your code, but not a 3rd party. An MCP needs to be designed as a product surface where the customer is the agent. Well defined tools and optimized context are super important. Otherwise you blow out an agent's context window with wasted information and cause it to thrash with multiple tool calls trying to accomplish a goal. It's like navigating blindly through the dark.