docstore-mcp
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_documentsA | Get a list of all indexed documents. Returns a list of document filenames that have been ingested. |
| searchA | Search indexed PDF documents for relevant chunks. Args: query: The search query text n_results: Maximum number of results to return (default: 5) document: Optional specific document filename to search within |
| get_document_infoA | Get information about a specific document including chunk count and metadata. Args: document: The filename of the document to get info for |
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 distinct purpose: listing documents, searching within them, and retrieving info about a specific document. No overlap in functionality.
Tools use snake_case. 'list_documents' and 'get_document_info' follow verb_noun, but 'search' is a bare verb, creating a minor inconsistency.
Three tools is minimal for a document store. While the core operations of listing, searching, and getting info are present, the set feels sparse for a full-featured server.
The server lacks essential operations like adding or deleting documents. Without ingestion or removal tools, the surface is incomplete for managing a document store.