Skip to content

feat(optimize): MCP tool coverage detector with cache-aware costing #223

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
iamtoruk merged 4 commits into from
May 5, 2026
Merged

feat(optimize): MCP tool coverage detector with cache-aware costing #223

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
1a080a0
feat(optimize): MCP tool coverage detector with cache-aware costing
ozymandiashh May 5, 2026
e46b20b
fix(optimize): reuse mcp coverage and type schema estimator
ozymandiashh May 5, 2026
735f41b
Fix cache-write pricing and shell-quote server names in fix commands
iamtoruk May 5, 2026
5120ec6
Merge origin/main into feat/mcp-tool-coverage
iamtoruk May 5, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 11 additions & 0 deletions CHANGELOG.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -2,6 +2,17 @@

## Unreleased

### Added (CLI)
- **MCP tool coverage detector.** New `optimize` finding flags MCP servers
whose tool inventory is largely unused. Inventory is observed from the
Claude `deferred_tools_delta` JSONL attachments (exact tool names per
session) instead of guessed at five tools per server. Token-savings
estimates are cache-aware: schema bytes pay full input price on the first
cache-creation turn of a session, then carry at the cache-read discount
on subsequent turns, capped per call so we never claim more overhead
than the call's own cache buckets could contain. Threshold:
>10 tools available, <20% coverage, observed in ≥2 sessions. Closes #2.

### Fixed (CLI)
- **`all` period semantics unified between CLI and dashboard.** The dashboard treated `--period all` as all-time (epoch start) while the CLI bounded it to the last 6 months. Both now consistently mean "Last 6 months". Period helpers (`Period`, `PERIODS`, `PERIOD_LABELS`, `toPeriod`, `getDateRange`) consolidated into `cli-date.ts`. Use `--from` / `--to` for unbounded historical ranges.

Expand Down
Loading
Loading