PyContextify
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
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| index_filebaseA | Index a filebase (directory tree or single file) for semantic search. This is the unified indexing function that handles all file types (code, documents, PDFs) with a single consistent pipeline. |
| discoverA | Discover all indexed tags. Returns a list of unique tag names from all indexed content, useful for browsing and filtering indexed material. Returns: Dictionary with: - tags: Sorted list of unique tag names - count: Number of unique tags |
| searchA | Perform semantic search across all indexed content. This function searches for content similar to the provided query across all indexed codebases and documents using vector similarity. The default output format is structured data for programmatic use. |
| reset_indexA | Reset the entire knowledge index, clearing all indexed content. This function clears all indexed data from memory and optionally removes saved index files from disk. This is a destructive operation that cannot be undone without re-indexing all content. |
| statusA | Get system status and comprehensive statistics. This function returns detailed information about the current state of the indexing system, including memory usage, indexed content statistics, embedding provider information, and persistence status. Returns: Dictionary with comprehensive system status and statistics |
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 5 tools
Each tool has a clear, distinct purpose: status for system info, reset_index for clearing, index_filebase for adding content, discover for listing tags, and search for querying. There is no overlap or ambiguity between these operations.
Most tool names are concise verbs (status, discover, search) while two use verb_noun (reset_index, index_filebase). The pattern is mostly consistent and readable, but not perfectly uniform in structure.
The server has 5 tools, which is well-scoped for an indexing and semantic search system. Each tool serves a necessary function without redundancy or bloat.
The core lifecycle is covered: add content (index_filebase), query (search), discover tags (discover), reset (reset_index), and monitor (status). A minor gap is the absence of a targeted delete/remove operation for specific content, but the reset option provides a workaround.