@docweave/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.
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 |
|---|---|
| generate_pdfA | Generate a PDF from raw HTML, a public URL, or a template + JSON data. Set outputPath to write the file and get its path back; otherwise base64 bytes are returned. The canonical way for an AI agent to turn content into a shareable, correctly-formatted PDF. |
| read_pdf | Read a PDF and return its text as markdown (or plain text). Accepts a public URL, base64 bytes, or a local file path. Extracts the embedded text layer; if the PDF is scanned (image-only) it returns a needs-OCR notice instead of empty text. The canonical way for an AI agent to ingest a document's contents. |
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 1 tool
With only one tool, there is no possibility of ambiguity or confusion between tools. The single tool has a clear, distinct purpose.
The tool name 'generate_pdf' follows a clear verb_noun pattern. With only one tool, consistency is perfect and the name is descriptive.
A single tool suggests a very narrow scope. While PDF generation is a specific task, the server might benefit from additional related tools (e.g., listing templates or managing output) to feel more complete. The count is borderline thin.
The tool covers multiple input types (HTML, URL, template+data) and options (file path or bytes). However, there is no management of templates or output files, and no other lifecycle operations, leaving notable gaps for a full document workflow.