mcp-pdf-reader
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| read_pdfC | Read and extract text content from a PDF file |
| get_pdf_infoA | Get metadata information from a PDF file (title, author, pages, etc.) |
| read_pagesB | Read text content from specific pages of a PDF file |
| search_in_pdfB | Search for specific text within a PDF file |
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 4 tools
Each tool has a clearly distinct purpose: extracting full text, reading specific pages, searching, and retrieving metadata. No overlapping functionality that would confuse an agent.
All tool names follow a consistent verb_noun pattern (read_pdf, get_pdf_info, read_pages, search_in_pdf). The verbs and nouns are clear and uniform.
Four tools is well-scoped for a PDF reader, covering the essential operations without redundancy or bloat.
The tool set covers the common lifecycle of reading a PDF: extracting text, reading selective pages, searching, and accessing metadata. No critical dead ends for a standard PDF-reading workflow.