4 ms·
> This is solved trivially by having default initial prompts. All majors tools like Claude Code or Gemini CLI have ways to set them up. That only makes it wors
by the_mitsuhiko 1y ago
> This is solved trivially by having default initial prompts. All majors tools like Claude Code or Gemini CLI have ways to set them up.
That only makes it worse. The MCP tools available all add to the initial context. The more tools, the more of the context is populated by MCP tool definitions.
- JyB 1y agoDo you mean that some tools (MCP clients) pass all functions of all configured MCP servers in the initial prompt? If that's the case: I understand the knee-jerk reaction but if it works? Also what theoretically prevents altering the prompt chaining logic in these tools to only expose a condensed list of MCP servers, not their whole capabilities, and only inject details based on LLM outputs? Doesn't seem like an insurmountable problem.
- the_mitsuhiko 1y ago> Do you mean that some tools (MCP clients) pass all functions of all configured MCP servers in the initial prompt? Not just some, all. That's just how MCP works. > If that's the case: I understand the knee-jerk reaction but if it works? I would not be writing about this if it worked well. The data indicates that it worse significantly worse than not using MCP because of the context rot, and the low too utilization.
- JyB 1y agoI guess I don't see the technical limitation. Seem like a protocol update issue.