PDFtotext 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_pdf_textB | Extract text content from a PDF file using pdftotext from poppler-utils |
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's purpose is clearly defined and distinct by default.
The single tool name follows a clear verb_noun pattern (read_pdf_text), 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 most practical server purposes, as it severely limits functionality and flexibility. While it might suffice for a minimal use case, it feels thin and incomplete for broader PDF processing needs.
The server's domain appears to be PDF text extraction, but with only one tool, there are significant gaps. For example, there are no tools for handling metadata, images, tables, or other PDF features, making the surface severely incomplete for typical PDF processing tasks.