Custom PDF 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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| read_pdf_textB | |
| get_pdf_infoB | |
| list_pdfs_in_directoryB | |
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 3 tools
Each tool has a clearly distinct purpose: get_pdf_info retrieves metadata, list_pdfs_in_directory enumerates files, and read_pdf_text extracts content. There is no overlap in functionality, making tool selection unambiguous for an agent.
All tool names follow a consistent verb_noun pattern with snake_case: get_pdf_info, list_pdfs_in_directory, and read_pdf_text. The naming is predictable and readable throughout the set.
With 3 tools, the server is well-scoped for basic PDF operations, but it feels slightly thin as it lacks tools for creating, editing, or deleting PDFs. However, the tools provided are essential and earn their place.
The server covers core read-only operations (info, listing, text extraction) but has notable gaps in the PDF lifecycle, such as creation, modification, merging, or deletion. Agents can work around this for basic tasks, but advanced workflows may be limited.