Compact MCP schemas and unify task tools #125
Loading…
Reference in a new issue
No description provided.
Delete branch "feature/mcp-schema-compaction"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Summary
task_*MCP family for root and nested tasks while retaining REST and CLI compatibility aliasesThe full local MCP catalog with file tools falls from 39,827 to 30,133 serialized characters, a 24.3% reduction. It contains 68 tools, no
subtask_*aliases, no generated$schemafields, and no explicitly emitted default annotation values.Research against the current MCP specification and Codex and Claude client behavior found no standard client-negotiated profile mechanism. Native client tool search and authorization-scoped filtering remain the preferred ways to reduce model context beyond this static compaction.
Verification
bun run check:qualitykReview review
Verdict: no findings
No concrete correctness, security, data-integrity, concurrency, or compatibility defects are established by the visible changes and verified repository context.
Reviewed by kReview at
8ad755410e. This comment is conservative and based only on the PR diff, metadata, and supplied repository context.Est. cost ~$1.38 (540.3k in / 2.7k out / gpt-5.6-sol).