whittle-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
Use these tools when a command or file would produce long output (test runs, logs, JSON, diffs, API specs). Pass a file path, not the text itself: sending the text through a tool call costs the tokens you want to save. Every result ends with a receipt line. Omitted parts are marked and can be fetched back with expand.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| trim_testsA | Shrink test-runner output (pytest, unittest, jest, go test, cargo test) to the failures and the summary. Use it instead of reading a whole test log. Omitted parts can be fetched with expand. |
| trim_logA | Shrink a log or stack trace: repeated lines collapse, long tracebacks keep their last frames, every distinct error line stays. Use it instead of reading a whole log. |
| mask_jsonA | Show the shape of a large JSON document: every key path stays, long arrays and strings are shortened. Use it to see what a big API response contains; fetch details with expand and a path such as $.items[3]. |
| trim_diffA | Shrink a git unified diff: lockfiles, generated files and whitespace-only changes collapse to one line each, and context around changes is cut. The result is for reading, not for applying. |
| slice_openapiA | Read a large OpenAPI document cheaply: with no filters you get an index of operations; with filters you get only the matching operations and the schemas they use. |
| expandA | Get back text that a trim omitted. Give the id and, ideally, the line range or JSON path from the marker. |
| reportA | Tokens saved in this session, net of anything re-expanded, and the money saved at EXAMPLE prices. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 7 tools
Each tool has a distinct target artifact or meta-operation: logs, test output, diffs, JSON, OpenAPI, expansion, and reporting. The closest overlap is trim_log vs trim_tests, but their input formats and outputs are clearly differentiated. expand and report are also clearly separate as retrieval and analytics tools.
All names use snake_case and are readable. The trim_* family is consistent, while mask_json and slice_openapi follow a verb_noun pattern, but expand and report are bare verbs. This is a minor deviation rather than a confusing mix.
Seven tools is well-scoped for a token-reduction server. Each tool covers a distinct artifact type or meta-operation, and none feels redundant or padded.
The surface covers common large-output cases: tests, logs, diffs, JSON, and OpenAPI, plus expansion and savings reporting. A generic trim tool for arbitrary text and a way to list active markers/sessions would round it out, but the main workflows are covered.