code-context-gate
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CODE_CONTEXT_GATE_ROOT | No | Root directory to search within. If not set, falls back to --project-root CLI flag or process.cwd(). |
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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| locateA | Find where a symbol or concept is defined or referenced — returns locations only, no source bodies |
| readC | Read a symbol or file:start-end range — block-expanded and size-bounded |
| exploreC | Structural questions: callers, callees, dependencies, impact, architecture overview |
| searchB | Keyword or regex search — sanctioned replacement for grep, always filtered and gated |
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 4 tools
Each tool has a clearly distinct purpose: locate finds definitions/references without source bodies, read retrieves source content, explore answers structural questions like callers/dependencies, and search performs text pattern matching. Descriptions cleanly separate these concerns.
All tool names are single, lowercase imperative verbs (locate, read, explore, search), following a consistent and predictable convention. No mixing of styles or ambiguous naming.
Four tools is well-scoped for a code-context gate. Each tool serves a distinct and necessary function in code navigation and understanding, with no obvious redundancy or missing essential operations.
The set covers core code context needs: finding symbols (locate), reading code (read), exploring relationships (explore), and searching text (search). A minor gap is the absence of a dedicated tool for listing all symbols in a file or repository overview, though explore may partially address this.