MCP tool surface
The tool API the agent sees. Design principles: a few powerful tools rather than many narrow ones, summary-first output, and handles over payloads.
Principles
- Few, powerful tools- keeps the agent's tool list small and the schema token cost low.
- Summary-first output - every tool defaults to
verbosity: "summary"; the agent escalates withinspect_responsewhen it needs more. - Handles over payloads - large results are referenced by id, not inlined into the response.
Tools by category
Filter the surface by category. Each card shows the tool name, signature, and a short description.
Verbosity & token optimization
verbosity: fullis auto-downgraded tosummarywhenextractis set - extracted values already contain the needed data.- WS/SSE frame and event arrays are capped at 10 items in
fullverbosity with truncation markers. graphql_introspectreturns enriched schemas: field signatures (name(args): Type), 1-level nested fields, inline input types, and enum values.inspect_responsesupports RFC 9535 JSONPath with filters ($.items[?@.id==1]),maxItemstruncation, and surfaces parse errors. For introspection results it reads the enrichedschemafield, so$.queries,$.mutations, and$.inputTypeswork directly.- Tool descriptions are kept short to minimize
tools/listtoken weight.