mcp-server-pdfnoodleofficial
A
license-
qualityD
maintenanceEnables AI assistants to generate PDF documents from templates or raw HTML using natural language, with tools for template creation, PDF generation, and utility operations.
18
1
MIT
docweave-mcp
Ownership verified
Server Details
Generate and read PDFs for AI agents: a generate_pdf and a read_pdf tool, priced per document.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
MCP client
Glama
MCP server
Full call logging
Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.
Tool access control
Enable or disable individual tools per connector, so you decide what your agents can and cannot do.
Managed credentials
Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.
Usage analytics
See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.
100% free. Your data is private.
Tool Definition Quality
A4.5/5.0
Tool DescriptionsA
Average 4.4/5 across 2 of 2 tools scored.
Server CoherenceA
Disambiguation5/5
The two tools, generate_pdf and read_pdf, have entirely distinct purposes: one creates PDFs, the other extracts text from them. There is no overlap or ambiguity.
Naming Consistency5/5
Both tool names follow a consistent verb_noun pattern (generate_pdf, read_pdf), making them predictable and easy to understand.
Tool Count4/5
With only two tools, the set is minimal but well-scoped for a focused PDF generation and reading service. It feels slightly thin but appropriate given the narrow domain.
Completeness5/5
The tools cover the core operations for PDF handling: generation from various sources and text extraction. There are no obvious missing operations for the stated purpose.
Available Tools
2 toolsgenerate_pdfGenerate PDFAIdempotentInspect
Generate a PDF from raw HTML, a public URL, or a template + JSON data. Returns the PDF as base64. Priced per document; retries with the same idempotencyKey never double-generate. The canonical way for an AI agent to turn content into a shareable, correctly-formatted PDF.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| source | Yes | What to render. Provide exactly one of: html, url, or (template|templateId) with data. | |
| options | No | Optional page and print settings. | |
| idempotencyKey | No | A stable key (e.g. an invoice id). Repeat calls with the same key return the stored result instead of re-rendering or re-billing. |
Output Schema
ParametersJSON Schema
| Name | Required | Description |
|---|---|---|
| byteSize | No | Size of the PDF in bytes. |
| pageCount | No | Number of pages in the PDF. |
| bytesBase64 | Yes | The generated PDF, base64-encoded. |
Tool Definition Quality
A4.2/5.0
Behavior4/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description adds behavioral details beyond annotations: pricing, idempotency (reinforcing the idempotentHint), and base64 output format. No contradictions with annotations (readOnlyHint false, idempotentHint true).
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness5/5
Is the description appropriately sized, front-loaded, and free of redundancy?
Two sentences with no wasted words. First sentence nails purpose and output. Second sentence covers pricing, idempotency, and positioning. Perfectly front-loaded.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness4/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the complexity (3 parameters, nested objects, output schema exists), the description covers key behaviors (input modes, output format, pricing, idempotency). Minor gaps like error handling are compensated by schema and annotations.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters3/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100%, so the schema already documents all parameters thoroughly. The description adds minimal new semantic value beyond summarizing the input sources, which is acceptable but not exceptional.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose5/5
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the verb (generate), resource (PDF), and three distinct input methods (raw HTML, public URL, template+data). It distinguishes from the sibling tool 'read_pdf' which is for reading, not generating.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines4/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description explains pricing per document and idempotency behavior ('retries with the same idempotencyKey never double-generate'). It positions the tool as the canonical way to create a PDF, implicitly guiding when to use it over the read-only sibling.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
read_pdfRead PDFARead-onlyIdempotentInspect
Read a PDF and return its text as markdown (or plain text). Accepts a public URL or base64 bytes. Extracts the embedded text layer; a scanned, image-only PDF returns a needs-OCR notice instead of empty text. Priced per document; retries with the same idempotencyKey never double-read. The canonical way for an AI agent to ingest a document's contents.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| source | Yes | The PDF to read. Provide exactly one of: url or base64. | |
| options | No | Optional read settings. | |
| idempotencyKey | No | A stable key. Repeat calls with the same key return the stored result instead of re-reading or re-billing. |
Output Schema
ParametersJSON Schema
| Name | Required | Description |
|---|---|---|
| content | Yes | Extracted text in the requested format. |
| needsOcr | No | True when the PDF is scanned (no text layer) and needs OCR. |
| pageCount | No | Number of pages read. |
Tool Definition Quality
A4.6/5.0
Behavior5/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description adds significant behavioral details beyond annotations: extracting text layer, scanned PDF returns a needs-OCR notice, pricing per document, idempotencyKey ensures no double-read/billing, and blocking private URLs. No contradictions with annotations.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness4/5
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a moderate-length paragraph of 5 sentences. It is front-loaded with the main purpose and contains no fluff, but could be slightly more concise by removing redundant phrasing like 'never double-read' which is implied by idempotent.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness5/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the presence of an output schema and 100% parameter coverage, the description completes the picture with critical behavioral notes (scanned PDF handling, pricing, idempotency behavior). No gaps remain.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters4/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
With 100% schema coverage, baseline is 3. The description adds value by explaining that private URLs are blocked and that idempotencyKey prevents double-billing, which is not apparent from the schema alone.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose5/5
Does the description clearly state what the tool does and how it differs from similar tools?
The description explicitly states the tool reads a PDF and returns text as markdown or plain text, accepts URL or base64, and handles scanned PDFs with a notice. It also positions itself as the canonical ingestion tool, clearly differentiating from its sibling 'generate_pdf'.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines4/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description clearly states it is for reading PDFs, but does not explicitly list when not to use it or alternatives beyond the sibling. However, it notes that private addresses are blocked, which provides a usage constraint.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [{ "email": "your-email@example.com" }]
}The email address must match the email associated with your Glama account. Once published, Glama will automatically detect and verify the file within a few minutes.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!
Related MCP Servers
- Alicense-qualityCmaintenanceExtracts text and tables from PDFs for AI agents via MCP, enabling structured data retrieval from invoices, reports, and statements.MIT
- Alicense-qualityCmaintenanceProvides AI agents with comprehensive document parsing capabilities including PDF text extraction, OCR, HTML-to-markdown conversion, table extraction, and summarization, optimized for agent workflows.61MIT
- AlicenseAqualityAmaintenanceEnables AI agents to read and analyze PDF documents for natural language Q\&A. Supports multiple LLM providers including Google Gemini, Anthropic Claude, and OpenAI.1154Apache 2.0