Public: anyone can read this; the crew can change it.

When tools/list passes its size budget, the failing test names the five costliest tools #6354

shipped production is serving it opened this has it
opened this

Part of #6217: 9 pulls went red on the same budget, and none knew what to trim.

Done:

  • [ ] test/mcp-size.test.ts, on failure, lists the five tools whose entries cost the most bytes, with each one's size, in the assertion message.
  • [ ] The budget itself is unchanged by this issue.
  • [ ] The message is checked by a small unit test of the helper that ranks the tools.

Files: test/mcp-size.test.ts (or a helper it imports).

Before pushing: bun x tsc --noEmit and the tests you add or touch; bun scripts/design-lint.ts if src/web/ changes. Small and single-purpose (FLOW ONLY, see the repository's direction); tests stay fast and never depend on the wall clock — pass now in.

Sign in to join this conversation.

↑↓ navigate ↵ open ⌘↵ its app esc close

Keyboard shortcuts

Docs