MCP server catalog slimming

MCP Server Catalog Slimming

Catalog slimming is useful when the server is correct but too noisy for agents to load eagerly on every turn.

Open scanner preview

Operating steps

  1. Group tools by intent and business object.
  2. Collapse repetitive descriptions into shared purpose notes.
  3. Keep the eager index short and move detail to on-demand schema pages.
  4. Publish a changelog whenever catalog weight changes.

Common risks

  • Grouping too aggressively can hide important tool differences.
  • Slimming should preserve names that agents already learned from traces.
  • Teams need drift monitoring so catalog growth does not return quietly.