MCP tool loading causes context pollution - need lazy loading or tool consolidation. #282699

Problem:
With MCP servers enabled, users quickly exceed 128 tools (I hit 137 with just GitHub MCP + built-in tools), causing degraded tool calling performance. All enabled tools are loaded into context on every turn, regardless of whether they're needed.

Current behavior:

Each MCP server provides dozens of granular tools
GitHub MCP alone: ~40 tools (create_issue, update_issue, close_issue, create_pr, update_pr, etc.)
All tools loaded into context simultaneously
Warning appears at >128 tools

Proposed solutions:

Lazy loading: Add a "tool manager" layer that analyzes user intent and loads only relevant tool groups on-demand

Tool consolidation: MCP servers should provide fewer, parameterized tools (e.g., github_issues(action: "create"|"update"|"close") instead of separate tools per action)

Smart defaults: Auto-disable tool groups based on workspace type (e.g., disable Jupyter tools in PHP projects)

Impact:
Power users with multiple MCP servers will hit 300+ tools, making the system unusable without manual pruning.