codegraph
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 |
|---|---|
| index_repository_toolA | Index or refresh the repository graph. Incremental unless force=true. |
| graph_statusB | Row counts and where the database lives. |
| search_nodesC | Find functions, classes and modules by name, signature or docstring keyword. |
| get_nodeA | Look up one symbol by qname, unique bare name, or path:line. |
| query_graphC | Trace one relationship. Patterns: callers_of, callees_of, imports_of, imported_by, tests_for, subclasses_of, defines, defined_in. |
| get_impact_radiusB | Blast radius of changing a symbol: direct and transitive callers, importers, tests. |
| detect_changes_toolA | Risk-ranked symbols touched by the current diff (working tree vs HEAD, or base..HEAD when base is given). |
| get_review_contextC | Source snippets plus callers and tests for the given symbols. |
| get_architecture_overviewC | Languages, top-level packages, hub functions, entry points and external deps. |
| find_dead_codeB | Callables with no callers, tests or subclasses. Candidates, not verdicts. |
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 10 tools
Each tool has a fairly distinct purpose: query_graph traces a single relationship while get_impact_radius computes transitive blast radius, and search_nodes vs get_node differ by fuzzy search vs exact lookup. The only mild overlap is get_review_context, which bundles callers and tests that also appear in get_impact_radius, but the added source snippets keep it differentiated.
Most tools follow a clean verb_noun snake_case pattern (query_graph, get_impact_radius, find_dead_code, search_nodes, get_node). Two outliers carry a redundant '_tool' suffix (detect_changes_tool, index_repository_tool) and graph_status is noun-only, which are minor deviations rather than a broken convention.
Ten tools is well-scoped for a code-graph analysis server, covering setup, exploration, and analysis without redundancy. Every tool earns its place across the indexing/query/analysis lifecycle.
The surface covers the full workflow: indexing, status, symbol search/lookup, relationship tracing, impact analysis, diff risk, review context, architecture overview, and dead-code detection. Minor gaps exist (e.g. no explicit index deletion or cross-repo management), but core lifecycles are well covered.