pdf-guides
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GUIDE_INDEX | Yes | Path to the index.json built from a folder of PDF guides, passed as -e GUIDE_INDEX=$PWD/index.json when adding the MCP server. | |
| OPENAI_API_KEY | Yes | OpenAI API key used by the default chat/embeddings endpoints, passed as -e OPENAI_API_KEY=$OPENAI_API_KEY when adding the MCP server. | |
| SEARCH_THRESHOLD | No | Cosine similarity threshold for search. The default is 0.46, measured for the bge-m3 embedding model; set this if using another embedding model. | 0.46 |
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_guidesA | Semantic search over the PDF guides. Returns the top passages, each with a citation label (guide, page) and a confidence score, or a note that nothing in the guides matches. |
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 a single tool there is no possibility of confusion between tools; its purpose (semantic search over PDF guides returning cited passages) is stated clearly. It cannot reach 5 only because there is no sibling tooling against which distinctness can be demonstrated.
The name search_guides follows a clean verb_noun snake_case convention that matches common MCP norms. With one tool the pattern cannot be verified across the surface, so this is a solid but not fully demonstrable 5.
A single search tool is defensible for a read-only PDF corpus, but it is thin even for that narrow scope — there is no companion for listing guides or retrieving a full guide/page. Borderline rather than clearly well-scoped.
Search is the core operation and it is well specified with citations and confidence, but the surface is a dead end: an agent given a citation label (guide, page) cannot fetch surrounding context, list available guides, or retrieve guide metadata.