distill
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DISTILL_MCP_MAX_TOKENS | No | Changes the maximum token cap for MCP tool results. Results are capped at 10,000 tokens by default. | 10000 |
| DISTILL_NO_SAVINGS_NOTE | No | Set to 1 to turn off the '[distill] tokens saved ≈ …' line at the end of MCP results. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| distill_fileA | Convert a document (PDF, DOCX, PPTX, XLSX, ODF, image) to token-lean Markdown; large documents come back in pages |
| distill_filesA | Convert up to 20 documents to token-lean Markdown; a failing file does not fail the call. Output is capped: a file that does not fit is returned in part and later files are skipped |
| distill_capabilitiesA | Report versions, limits and available features (LibreOffice, LLMLingua-2) |
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 3 tools
distill_file and distill_files overlap in purpose (singular vs batch conversion), which could cause a moment of hesitation, but the descriptions clearly differentiate single-document versus up-to-20-document batches. distill_capabilities is clearly distinct as a metadata/reporting tool.
All three tools use a consistent snake_case distill_<noun> pattern. The singular/plural distinction between distill_file and distill_files is a predictable and readable convention.
Three tools is a tight, well-scoped surface for a document-conversion server: one for single files, one for batch, and one for capability discovery. Each tool earns its place with no redundancy.
The surface covers single conversion, batch conversion, and capability reporting, which is the core lifecycle for this domain. A minor gap is the lack of an explicit continuation/retrieval mechanism for documents that come back in pages or partial output, which could create a dead end for large files.