repodigest-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 |
|---|---|
| get_symbol_signatureA | Return a Python symbol's signature and docstring without its body. Far cheaper than reading the file. Works for functions, classes (methods listed as signatures) and methods. Args:
symbol_name: Qualified name ( |
| get_symbol_dependenciesA | List a symbol's direct callers and callees across the repository. Edges are matched by simple name (no import or type resolution), so common names such
as Args:
symbol_name: Qualified name ( |
| pack_task_contextA | Pack the code most relevant to a task into a token-bounded XML snippet. Ranks every symbol against Args: query: Natural-language description of the task, e.g. "validate user login". budget: Max tokens (cl100k_base) of packed source. The XML markup around the source (file/symbol tags, usage summary) is not counted, so allow ~10% headroom. signatures_only: Pack everything except the root symbol as signature + docstring. path: Repository root to search (default: the server's working directory). |
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
get_symbol_signature and get_symbol_dependencies share the same argument shape and both target a single symbol, so an agent could briefly confuse them; however, their outputs are clearly different (docstring vs. call graph). pack_task_context is unmistakably distinct in purpose.
The get_symbol_* prefix establishes a clear pattern for the two lookup tools, and pack_task_context uses the same snake_case verb_noun style. The one-off pack_ verb is a minor deviation rather than a chaotic mix.
Three tools is a focused, purposeful set for a code-digestion server: signature lookup, dependency lookup, and context packing. Each tool fills a clear niche without redundancy.
The core workflow of inspecting a symbol and packing relevant code for a task is well covered. Missing capabilities like repository-wide symbol discovery or batch queries are minor gaps since pack_task_context effectively provides search.