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 | Reads content/metadata from PDFs. Paths must be relative to the project root. Project root can be set via: 1) --root command line argument, 2) PDF_READER_MCP_ROOT environment variable, or 3) process.cwd() (default). Absolute paths in the path parameter are rejected. |
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 between tools. The tool 'read_pdf' has a clear and distinct purpose that cannot be confused with any other tool in this set.
The single tool name 'read_pdf' follows a clear verb_noun pattern, and with only one tool, consistency is inherently perfect as there are no other names to compare against.
A single tool is too few for a server named 'PDF Reader MCP Server', which implies broader PDF-related functionality. This minimal set feels thin and under-scoped for the apparent domain, limiting agent capabilities.
The tool surface is severely incomplete for a PDF reader domain. While 'read_pdf' handles content extraction, there are obvious gaps such as no tools for creating, editing, merging, splitting, or searching PDFs, which are common operations in this context.