[FEATURE] Add configuration option to force MCP tool lazy loading (Tool Search)

Preflight Checklist

• [x] I have searched existing requests and this feature hasn't been requested yet
• [x] This is a single feature request (not multiple features)

Problem Statement

When working with moderate numbers of MCP tools (~50) that fall just under the 10% context threshold, there's no way to enable lazy loading. Users who are context-conscious would benefit from lazy loading even when not strictly required, preserving context for actual work rather than tool schemas that may not be used.

Proposed Solution

Add a setting in settings.json:

{
  "mcpToolSearch": "auto" | "always" | "never"
}

• auto (default): Current behavior, triggers at 10% threshold
• always: Force lazy loading regardless of tool count
• never: Always load all tool schemas upfront

Alternative Solutions

• Artificially inflate MCP tool count to cross the 10% threshold (not practical)
• Lower the threshold percentage globally (less flexible than explicit user control)
• No workaround currently exists for users who want lazy loading with moderate tool counts

Priority

Medium - Would be very helpful

Feature Category

CLI commands and flags

Use Case Example

Example scenario:

1. I have 2 MCP servers with ~50 total tools (claude-in-chrome + playwright)
2. These tools fall just under the 10% context threshold
3. With this feature, I could set "mcpToolSearch": "always" to force lazy loading
4. This would save context for actual coding work instead of tool schemas I may not use in a given session

Additional Context

_No response_