PDF Extraction MCP Server
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| extract-pdf-contentsC | Extract contents from a local PDF file, given page numbers separated in comma. Negative page index number supported. |
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 overlap with other tools. The tool's purpose is clearly defined as extracting contents from PDF files, making it impossible for an agent to confuse it with another tool.
Since there is only one tool, naming consistency is inherently perfect. The tool name 'extract-pdf-contents' follows a clear verb-noun pattern, and there are no other tools to deviate from or conflict with this pattern.
A single tool for a PDF extraction server is too minimal for the apparent scope. While the tool handles content extraction, typical PDF operations like metadata retrieval, text analysis, or format conversion are missing, making the server feel incomplete and underpowered for its domain.
The server is severely incomplete for PDF extraction. It only provides content extraction with page selection, lacking essential operations such as getting metadata, extracting images, converting to other formats, or searching within PDFs. This will likely cause agent failures when broader PDF tasks are required.