Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

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

CapabilityDetails
tools
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
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 grep -rn "function X" or reading files to locate a definition: pre-indexed, no false positives from comments or strings, sub-millisecond. Pass substring:true for partial-name searches. Do NOT use for "who calls X?" — use gp_callers for that.

gp_callersA

List every caller of a symbol (direction=callers) or everything it calls (direction=callees). ALWAYS use instead of grep -rn "X(" for "who calls X?" — pre-indexed reverse map, sub-millisecond, no false positives from comments or strings. Use direction=callers to find dependents before a rename; direction=callees to understand what a function depends on. Do NOT use for full blast-radius analysis across multiple hops — use gp_impact instead.

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 git diff | xargs grep with a single structured answer. Pass since: <commit|branch> to scope callers to files changed since that ref (ideal for PR review or refactor scoping). Do NOT use just to see direct callers; use gp_callers for that.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A4.4/5.0

Scored across 4 tools

Disambiguation5/5

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.

Naming Consistency4/5

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.

Tool Count5/5

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.

Completeness4/5

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.

Maintenance

ActivityInactive
ResponsivenessResponsive