mcp-pdf-tools

by hanweg

Overview Schema Related Servers Score Discussions

Python

Local

Server Quality Checklist

Profile completionA complete profile improves this server's visibility in search results.

Latest release: v1.0.0
Disambiguation3/5
There is some overlap between tools like 'merge-pdfs' and 'merge-pdfs-ordered', which could cause confusion as both handle merging but with different ordering approaches. However, other tools like 'extract-pages' and 'search-pdfs' have distinct purposes, and descriptions help clarify the differences between merging variants.
Naming Consistency5/5
All tool names follow a consistent verb-noun pattern with hyphen separation (e.g., 'extract-pages', 'merge-pdfs'), making them predictable and readable. There are no deviations in naming conventions across the set.
Tool Count5/5
With 5 tools, this server is well-scoped for PDF manipulation tasks, covering extraction, merging, and searching without being overly complex or too sparse. Each tool appears to serve a specific and necessary function in the domain.
Completeness4/5
The tool set covers key PDF operations like extraction, merging, and searching, with 'find-related-pdfs' adding a unique content-based feature. A minor gap is the lack of tools for PDF creation or editing (e.g., adding text or images), but core workflows are adequately supported for a focused PDF utility server.
Average 3/5 across 5 of 5 tools scored.
See the Tool Scores section below for per-tool breakdowns.
- No community issues in the last 6 months
- 0 commits in the last 12 weeks
- No stable releases found
- No critical vulnerability alerts
- No high-severity vulnerability alerts
- No code scanning findings
- CI status not available
This repository is licensed under The Unlicense.
This repository includes a README.md file.
No tool usage detected in the last 30 days. Usage tracking helps demonstrate server value.
Tip: use the "Try in Browser" feature on the server page to seed initial usage.
Add a glama.json file to provide metadata about your server.
If you are the author, simply .
If the server belongs to an organization, first add glama.json to the root of your repository:
```
{
  "$schema": "https://glama.ai/mcp/schemas/server.json",
  "maintainers": [
    "your-github-username"
  ]
}
```
Then . Browse examples.
Add related servers to improve discoverability.

How to sync the server with GitHub?

Servers are automatically synced at least once per day, but you can also sync manually at any time to instantly update the server profile.

To manually sync the server, click the "Sync Server" button in the MCP server admin interface.

How is the quality score calculated?

The overall quality score combines two components: Tool Definition Quality (70%) and Server Coherence (30%).

Tool Definition Quality measures how well each tool describes itself to AI agents. Every tool is scored 1–5 across six dimensions: Purpose Clarity (25%), Usage Guidelines (20%), Behavioral Transparency (20%), Parameter Semantics (15%), Conciseness & Structure (10%), and Contextual Completeness (10%). The server-level definition quality score is calculated as 60% mean TDQS + 40% minimum TDQS, so a single poorly described tool pulls the score down.

Server Coherence evaluates how well the tools work together as a set, scoring four dimensions equally: Disambiguation (can agents tell tools apart?), Naming Consistency, Tool Count Appropriateness, and Completeness (are there gaps in the tool surface?).

Tiers are derived from the overall score: A (≥3.5), B (≥3.0), C (≥2.0), D (≥1.0), F (<1.0). B and above is considered passing.

Tool Scores

Behavior2/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries the full burden of behavioral disclosure. It describes the tool's function but lacks critical details: it doesn't specify whether this is a read-only or mutating operation, what permissions are needed, how results are returned (e.g., list format, error handling), or any rate limits. For a tool with 4 parameters and no annotation coverage, this is a significant gap in transparency.
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?
The description is a single, efficient sentence that front-loads the core purpose without unnecessary details. Every word earns its place by clearly stating what the tool does, making it easy for an agent to parse quickly. There's no redundancy or fluff.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness2/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the tool's complexity (4 parameters, content analysis functionality) and lack of annotations and output schema, the description is incomplete. It doesn't cover behavioral aspects like mutation risks, return values, or error conditions. While the schema handles parameters well, the overall context for safe and effective use is insufficient, especially for a tool that likely involves file system operations.
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 description coverage is 100%, so the input schema fully documents all parameters. The description adds no additional parameter semantics beyond what's in the schema—it doesn't explain relationships between parameters (e.g., how 'pattern_matching_only' interacts with 'min_pattern_occurrences') or provide usage examples. This meets the baseline for high schema coverage but doesn't enhance understanding.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose4/5
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool's purpose: 'Find a PDF and then search for related PDFs based on its content, including common substring patterns.' This specifies the verb (find and search), resource (PDFs), and method (content analysis with substring patterns). However, it doesn't explicitly distinguish this from sibling tools like 'search-pdfs' or 'extract-pages,' which prevents a perfect score.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines2/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description provides no guidance on when to use this tool versus alternatives. It doesn't mention sibling tools like 'search-pdfs' or 'extract-pages,' nor does it specify prerequisites or exclusions. This leaves the agent without context for tool selection, relying solely on the description's implied purpose.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Behavior2/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries the full burden of behavioral disclosure. It states the action ('merge') but doesn't cover critical traits like whether it modifies original files, handles errors, requires specific permissions, or has performance limits. This leaves significant gaps in understanding the tool's behavior.
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?
The description is a single, clear sentence that directly states the tool's function without unnecessary words. It's front-loaded and efficiently communicates the core purpose, making it highly concise and well-structured.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness2/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the complexity of merging files and the lack of annotations and output schema, the description is insufficient. It doesn't explain return values, error handling, or behavioral nuances, leaving the agent with incomplete information for reliable tool invocation in a real-world context.
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 description coverage is 100%, so the input schema fully documents the two parameters ('input_paths' and 'output_path'). The description adds no additional semantic context beyond what the schema provides, such as file format details or merging order, meeting the baseline for high schema coverage.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose4/5
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the action ('merge') and resource ('multiple PDF files into a single PDF'), making the purpose immediately understandable. However, it doesn't differentiate from sibling tools like 'merge-pdfs-ordered', which suggests a similar function with ordering, leaving room for improvement in sibling distinction.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines2/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description provides no guidance on when to use this tool versus alternatives like 'merge-pdfs-ordered' or other PDF-related siblings. It lacks context on prerequisites, such as file accessibility or format requirements, leaving usage unclear without external knowledge.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Behavior2/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries the full burden of behavioral disclosure. It states the search action but lacks critical details such as permission requirements, error handling (e.g., invalid paths), performance implications (e.g., large directories), or output format (e.g., list of file paths). This is a significant gap for a tool with potential side effects like file system access.
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?
The description is a single, efficient sentence that front-loads the core purpose ('Search for PDF files in a directory') and adds a concise modifier ('with optional pattern matching'). There is no wasted text, making it easy for an agent to parse quickly.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness2/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the lack of annotations and output schema, the description is incomplete. It doesn't explain what the tool returns (e.g., a list of file paths, metadata), error conditions, or behavioral nuances like recursion depth limits. For a search tool with file system interaction, this leaves the agent under-informed about critical operational aspects.
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?
The schema description coverage is 100%, so the input schema fully documents all three parameters (base_path, pattern, recursive). The description adds no additional semantic context beyond implying pattern matching, which is already covered in the schema. This meets the baseline for high schema coverage.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose4/5
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool's purpose with a specific verb ('Search') and resource ('PDF files in a directory'), and includes the optional capability ('pattern matching'). It doesn't explicitly distinguish from sibling tools like 'find-related-pdfs', but the focus on file search is clear and non-tautological.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines2/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description provides no guidance on when to use this tool versus alternatives like 'find-related-pdfs' or other siblings. It mentions optional pattern matching but doesn't specify scenarios or exclusions, leaving the agent to infer usage from the tool name alone.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Behavior2/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries the full burden of behavioral disclosure. It states the action ('extract') but doesn't mention whether this is a read-only or destructive operation, potential side effects (e.g., file creation at output_path), error conditions, or performance considerations. This leaves significant gaps in understanding how the tool behaves beyond its basic function.
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?
The description is a single, direct sentence that efficiently conveys the core function without any wasted words. It is appropriately sized and front-loaded, making it easy for an agent to parse quickly and understand the tool's purpose at a glance.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness3/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the tool's moderate complexity (file manipulation with three parameters) and lack of annotations or output schema, the description is minimally adequate. It covers the basic action but omits critical context like behavioral traits, usage guidelines, and output details, leaving the agent with incomplete information for safe and effective invocation.
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?
The schema description coverage is 100%, with clear documentation for all three parameters (input_path, output_path, pages). The description adds no additional semantic context beyond what the schema provides, such as file format requirements or page numbering specifics, so it meets the baseline for adequate but not enhanced parameter understanding.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose4/5
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the action ('extract specific pages') and resource ('from a PDF file'), making the tool's purpose immediately understandable. However, it doesn't differentiate from sibling tools like 'merge-pdfs' or 'search-pdfs' beyond the basic function, which prevents a perfect score.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines2/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description provides no guidance on when to use this tool versus alternatives like 'merge-pdfs' or 'search-pdfs'. It lacks any context about prerequisites, such as needing an existing PDF file, or exclusions, leaving the agent to infer usage scenarios independently.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Behavior2/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden of behavioral disclosure. It mentions merging PDFs in order based on patterns, but doesn't cover critical aspects like whether this is a read-only or destructive operation, error handling, performance implications, or what the output looks like (e.g., file format, success indicators). For a tool with no annotations, this leaves significant gaps in understanding its behavior.
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?
The description is a single, efficient sentence that front-loads the core functionality ('merge PDFs in a specific order') and adds necessary detail ('based on patterns or exact names') without any wasted words. It's appropriately sized for the tool's complexity.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness2/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given no annotations and no output schema, the description is incomplete for a tool with 4 parameters that performs file operations. It doesn't explain what the merged output entails (e.g., file location, format), error conditions, or behavioral traits like whether it overwrites existing files. For a mutation tool with rich parameters, more context is needed to be fully helpful.
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 description coverage is 100%, so the schema already documents all parameters thoroughly. The description adds minimal value beyond the schema by hinting at the purpose of 'patterns' for ordering, but doesn't provide additional syntax, examples, or constraints. This meets the baseline of 3 when schema coverage is high.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose4/5
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool's purpose as merging PDFs in a specific order based on patterns or exact names, which includes a specific verb ('merge') and resource ('PDFs'). It distinguishes from the sibling 'merge-pdfs' by specifying ordering and pattern-based selection, though it doesn't explicitly contrast with other siblings like 'extract-pages' or 'search-pdfs'.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines3/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description implies usage when ordering and pattern-based selection are needed, suggesting it's for merging PDFs with specific ordering criteria. However, it lacks explicit guidance on when to use this tool versus alternatives like 'merge-pdfs' (which might merge without ordering) or other siblings, and doesn't mention prerequisites or exclusions.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

GitHub Badge

Glama performs regular codebase and documentation scans to:

Confirm that the MCP server is working as expected.
Confirm that there are no obvious security issues.
Evaluate tool definition quality.

Our badge communicates server capabilities, safety, and installation instructions.

Card Badge

Copy to your README.md:

[![mcp-pdf-tools MCP server](https://glama.ai/mcp/servers/hanweg/mcp-pdf-tools/badges/card.svg)](https://glama.ai/mcp/servers/hanweg/mcp-pdf-tools)

Score Badge

Copy to your README.md:

[![mcp-pdf-tools MCP server](https://glama.ai/mcp/servers/hanweg/mcp-pdf-tools/badges/score.svg)](https://glama.ai/mcp/servers/hanweg/mcp-pdf-tools)

Latest Blog Posts

Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)
By Om-Shree-0709 on July 25, 2026.
mcp
Agent Identity
OAuth 2.1
Your AI Chatbot Just Exposed Your CEO's Salary to an Intern
By Om-Shree-0709 on July 2, 2026.
Agent Identity
MCP Security
OAuth Delegation
Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)
By Om-Shree-0709 on June 30, 2026.
Agentic Ai
Prompt Injection
WebAssembly

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/hanweg/mcp-pdf-tools'

If you have feedback or need assistance with the MCP directory API, please join our Discord server