pdf-analyzer
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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| analyze_pdfA | Analyze a PDF document using AI. Provide an absolute file path, URL, cached file URI (from a previous response, Google only), or array of cached file URIs (from a previous chunked response, Google only) and a list of questions to ask about the PDF content. With the Google provider, returns a cached_uris array that can be reused for subsequent queries on the same document. |
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. The tool 'analyze_pdf' stands alone with a clear purpose.
The single tool 'analyze_pdf' follows a clear verb_noun pattern, which is standard and consistent.
A single tool for a PDF analyzer is too few. While the tool itself is non-trivial (AI analysis), the server lacks any additional operations like extraction, merging, or conversion, making it feel incomplete for typical PDF tasks.
The server only offers AI-based analysis of PDFs. There are obvious gaps such as missing CRUD operations for PDF content, text extraction, or file manipulation, which limits its usefulness.