PDF Reader 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 |
|---|---|
| read_pdfA | |
| get_pdf_metadataB | Quickly retrieve metadata from a PDF without reading the full content. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| summarize_pdf | Create a prompt to summarize a PDF document. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 2 tools
The two tools have clearly distinct purposes: get_pdf_metadata retrieves metadata without reading content, while read_pdf extracts the actual text, tables, and images. There is no overlap or ambiguity between these functions.
Both tools follow a consistent verb_noun pattern (get_pdf_metadata and read_pdf), using clear action verbs and the same domain prefix. The naming is predictable and readable throughout.
With only 2 tools, the server feels thin for a PDF reader domain. While the tools cover basic reading and metadata, there are likely missing operations like searching within PDFs, extracting specific elements, or handling annotations, which limits functionality.
The tool surface is significantly incomplete for a PDF reader. It lacks essential operations such as search, annotation handling, page manipulation, or conversion to other formats. Agents will face dead ends when trying to perform common PDF tasks beyond simple reading.