citegraph
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| --root | Yes | Absolute path to the folder containing the git repositories to serve (e.g. /absolute/path/to/my-repos). Used with the `citegraph serve` command. |
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 |
|---|---|
| statusA | Index status: repos, indexed commit vs current HEAD (stale), counts, last run. Call this first. |
| search_symbolsB | Fuzzy search symbol names. kind: module|class|interface|function|method. Returns path:line evidence. |
| get_symbolA | Look up one symbol (bare, qualified, or repo:qualified). Ambiguous names return candidates. |
| what_callsA | Callers of a symbol (depth 1-3). Each edge has rule, confidence and the path:line of the call. Edges below min_confidence (default 0.5) are hidden and counted in notes; pass min_confidence=0.1 to see lower-confidence candidates such as name-only (ambiguous) matches. |
| what_does_it_callA | Callees of a symbol (depth 1-3). Each edge has rule, confidence and the path:line of the call. Edges below min_confidence (default 0.5) are hidden and counted in notes; pass min_confidence=0.1 to see lower-confidence candidates such as name-only (ambiguous) matches. |
| find_pathB | Shortest call path from one symbol to another, following edges at or above min_confidence. |
| find_config_keyA | Where config keys are defined (json/yaml/env example) and read in code. |
| repo_overviewC | Languages, top modules, entry points and fan-in hotspots for one indexed repo. |
| explain_edgeB | Why citegraph believes from_symbol calls to_symbol: rule, meaning, confidence, evidence. |
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 9 tools
Each tool has a largely distinct purpose: get_symbol vs search_symbols (exact vs fuzzy) and what_calls vs what_does_it_call (inverse directions) are clearly separated by their descriptions. Minor overlap between status and repo_overview (both report index/repo state) is the only real friction, but descriptions disambiguate them.
Three conventions coexist: verb_noun (get_symbol, search_symbols, find_path, find_config_key, explain_edge), question-style (what_calls, what_does_it_call), and bare nouns (status, repo_overview). It remains readable but there is no single predictable pattern.
Nine tools is well-scoped for a call-graph/symbol-index server, with each tool covering a distinct query direction or diagnostic. No redundant or filler tools.
The core call-graph lifecycle is covered: status/lookup/search, bidirectional traversal, path finding, config tracing, repo overview, and edge explanation. Minor gaps exist (e.g. listing indexed repos explicitly or triggering a reindex), but agents can work around them.