tooldash-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| TOOLDASH_MCP_ROOT | No | Optional directory to restrict file access. Any path outside it is refused. Example: /home/you/Documents/pdfs |
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 |
|---|---|
| pdf_infoA | Report the page count, per-page dimensions and document metadata of a local PDF. Read-only: the file is never modified. Call this before merging or extracting so page numbers are known to be valid. |
| merge_pdfsA | Combine two or more local PDFs into a single file, in the order given. Runs entirely on this machine with pdf-lib — nothing is uploaded and no URL is fetched. Refuses to overwrite an existing output unless overwrite is true. |
| extract_pdf_pagesA | Write a selection of pages from a local PDF into a new file, leaving the original untouched. Pages are 1-based and may be given as a list and ranges, e.g. "1-3,7,10-12". Order is preserved, so "3,1" produces a two-page file in that order. |
| clean_textA | Normalize messy text: collapse repeated spaces, strip trailing whitespace and invisible characters, unify line endings, and optionally collapse blank lines, convert smart punctuation to ASCII, or remove URLs. Runs entirely offline — nothing is uploaded and no network call is made. |
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 4 tools
Each tool targets a distinct action: reading PDF metadata, merging PDFs, extracting pages, and normalizing text. There is no overlap or boundary ambiguity, so an agent can select the right tool confidently.
Three tools follow a clear verb_object pattern (merge_pdfs, extract_pdf_pages, clean_text), while pdf_info uses noun_noun rather than a verb-first form. This is a minor inconsistency in an otherwise predictable and readable naming scheme.
Four tools is a reasonable size for a focused utility server, and none of the tools feel redundant. The mix of PDF operations with a standalone text cleaner makes the scope slightly broad, but the count itself is not too thin or bloated.
The PDF workflow covers the key needs of inspection, merging, and page extraction, while clean_text works as a self-contained text utility. Missing operations like PDF text extraction, rotation, or encryption are plausible additions, but agents can complete core merge, extract, and cleanup tasks without dead ends.