MCP Demo - Document Search 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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_documentsA | Search indexed documents by keyword or phrase using TF-IDF ranking. Returns up to max_results results, each with a relevance score and excerpt. |
| get_documentA | Retrieve the full text of a document by filename. Call list_documents first if you're unsure of the exact filename. |
| list_documentsA | List every document currently in the index, along with its word count. |
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 all documents, searching by keyword, and retrieving full text. There is no overlap or ambiguity.
All tools follow a consistent verb_noun snake_case pattern: get_document, list_documents, search_documents.
With 3 tools, the server is well-scoped for document search: list, search, retrieve. Not too few or too many.
Core functionality is fully covered: indexing overview, search with ranking, and full-text retrieval. No gaps for a search-focused server.