doc-tools-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DT_BIB_CSL | No | Default path to CSL style file (.csl). Enables style-aware field validation on bib:validate, bib:add, bib:update. | |
| DT_BIB_YAML | No | Default path to CSL-YAML bibliography file. Makes 'file' param optional on all bib:* tools. | |
| DT_CT_REGISTRY | No | Default path to citation verification registry JSON. Makes 'registry_path' optional on all ctverify:* tools. |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| bib:getA | Retrieve a single bibliography entry by ID. Returns the full YAML block. |
| bib:searchA | Search bibliography entries across all fields: author, title, type, year, editor, container-title. Use ONE search term per call (e.g., "Pahlow" or "OLG Köln"). For multiple lookups, call this tool multiple times. |
| bib:listB | List all bibliography entries of a given CSL type (e.g., "legal_case", "book", "article-journal", "chapter"). |
| bib:existsA | Check if a citation ID exists in the bibliography. Fast boolean check before citing. |
| bib:statsA | Get bibliography statistics: total entry count and breakdown by CSL type. |
| bib:addA | Add a new bibliography entry. Validates required fields per CSL type, checks for duplicate IDs, and creates a .bak backup before writing. Returns the created YAML block for confirmation. |
| bib:updateA | Update fields of an existing bibliography entry. Only the specified fields are changed; all other fields remain untouched. Creates a .bak backup before writing. |
| bib:deleteA | Remove a bibliography entry by ID. Creates a .bak backup before writing. |
| bib:validateA | Validate the entire bibliography file: YAML syntax, required fields per CSL type, duplicate IDs, and missing issued dates. Returns a list of errors and warnings. |
| ctverify:extractA | Extract citations from Pandoc inline footnotes (^[...]) for verification tracking. This is a CITATION VERIFICATION tool, not bibliography management. It extracts citations so the LLM can systematically verify that each cited source actually supports the claim made in the text. Use |
| ctverify:updateA | Batch update citation verification entries. Each entry can set claim, status, and/or note independently. The |
| ctverify:statusB | Show verification progress of a citation registry: counts by status and list of citations. Use |
| ctverify:getA | Retrieve one or more citation entries by ID. Returns full details including cite, context, claim, status, and note. |
| ctverify:bulk-updateA | Update status (and optionally note) for multiple citations at once. Select entries either by a list of IDs or by filter (current status). At least one of |
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 14 tools
The bib:* and ctverify:* namespaces cleanly separate bibliography management from citation verification. Within each group, tools like get, search, exists, list, and stats have clearly distinct purposes, so an agent is unlikely to select the wrong one.
The namespace:action pattern is consistent and readable, with snake_case action names like bib:list and ctverify:bulk-update. The only minor deviations are noun-style actions such as bib:stats and ctverify:status, plus the hyphenated bulk-update.
Fourteen tools is well-scoped for a server covering bibliography management and citation verification. Each tool represents a distinct operation, and the split of 9 bibliography tools and 5 verification tools feels balanced without unnecessary bloat.
The bibliography side covers CRUD, search, validation, existence checks, and statistics, while the verification side covers extraction, status tracking, and batch updates. Minor gaps exist, such as no way to list all bibliography entries without specifying a CSL type and no delete operation for verification registry entries, but these are workable.