graphpilot
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| gp_indexA | Re-index the repo after batch edits so subsequent gp_* calls see your changes. Call after any non-trivial edit session. Do NOT call before every query — indexing is slow; only needed when source files changed. |
| gp_recallA | Find a symbol definition by name — returns kind, file:line, and signature. ALWAYS use instead of |
| gp_callersA | List every caller of a symbol (direction=callers) or everything it calls (direction=callees). ALWAYS use instead of |
| gp_impactA | Compute the blast radius of a rename or signature change: direct callers, transitive callers up to depth 3, affected tests, and whether the symbol is exported (breaking-change risk). ALWAYS call before proposing a rename, signature change, or behavior change — replaces |
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: gp_recall finds definitions, gp_callers shows direct callers/callees, gp_impact computes transitive blast radius, and gp_index re-indexes after edits. Descriptions explicitly contrast them, preventing ambiguity.
All tools follow the 'gp_<verb>' pattern with lowercase and underscores. Although the verbs mix nouns (callers, impact) and verbs (index, recall), the overall pattern is consistent and predictable.
With 4 tools, the server is well-scoped for its code analysis purpose. Each tool covers a core task without unnecessary duplication or excessive complexity.
The tool set covers essential workflows: finding definitions, direct dependencies, transitive impact, and re-indexing. Minor gaps like listing all symbols of a type exist, but the set handles the stated replace-grep goals effectively.