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
overviewA

Call first in an unfamiliar repository, before planning any change. Returns size, languages, call-graph shape (resolution rates, critical depth, the most central symbols by PageRank), the overall score, and the finding count.

find_symbolA

Call instead of grepping when you know part of a name but not where it lives. Matches exactly first, then by substring; returns kind, file:line, visibility, and entry-point status for each match, plus the total match count.

definition_ofA

Call to jump to where a symbol is defined before reading or editing it. Returns the definition sites with file:line, plus a provenance field saying whether the match was exact (fully qualified), exact (short name), or a substring fallback - so you know how much to trust it.

references_ofA

Call before renaming, changing a signature, or deleting a symbol. Returns resolved_references (exact call-graph edges with file:line) and name_match_references (dynamic or unresolved calls with the same final name) separately, so high- and low-confidence hits stay distinguishable.

callers_ofA

Call to answer "who uses this?" one level up. Returns the direct callers with exact call sites (file:line) from the resolved call graph - facts, not guesses. For the full blast radius use impact_of; for dynamic-dispatch hits too use references_of.

callees_ofA

Call to understand what a function does without reading its body, or to find its dependencies. Returns resolved callees with call sites, plus the unresolved names (external crates, stdlib) and dynamic calls it makes.

impact_ofA

Call before a breaking change to size its blast radius. Returns every symbol that transitively reaches this one and the files they live in - the set that could break if it changes, and the set worth reviewing or testing after. The symbol list is capped at 100; the count and file list are exact.

dead_codeA

Call before deleting code, or when asked what is unused. Returns the symbols with no resolved caller, no name-match caller, and no path from any entry point, each with a confidence score - dynamic dispatch and reflection lower it, so check anything below ~0.9 by hand.

auditA

Call after finishing an edit, and before telling the user the work is done. Runs the full deterministic audit - security, dead code, duplicates, naming, complexity, infrastructure - and returns the score plus the findings with file:line, severity and a suggested fix. Use min_severity to cut noise. For a diff-sized answer, prefer audit_delta.

audit_deltaA

Call to judge your own diff, or to review a branch, without wading through pre-existing findings. Returns only the findings in files changed versus a git ref (uncommitted and untracked files included). The whole tree is still analysed, so cross-file facts like dead code stay correct.

perf_adviceA

Call ONLY when the user asks about performance - it is advisory, not scored, and noisy otherwise. Returns the constructs that hurt the chosen objective (hot-path allocations, locks, unbounded channels, blocking-in-async), ranked by impact, each with locations and a concrete design fix such as a bounded ring buffer in place of an unbounded channel. Tuned for Rust; other languages give limited signal.

endpointsA

Call when changing an API route or a client fetch, or to check a frontend and backend still agree. Matches client HTTP calls (fetch/axios) to the route handlers that serve them across the language boundary, and returns the calls that hit NO route (likely 404s or typos) and the routes NO client calls (possibly dead) - findings a single-language tool cannot produce.

duplicatesA

Call before adding a helper, to check one already exists, or when consolidating repeated logic. Returns groups of duplicate implementations - exact, renamed (identifier-insensitive), and structural - each with a canonical pick to keep, the copies to remap onto it, and a confidence score.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A4.3/5.0

Scored across 13 tools

Disambiguation4/5

Each tool has a distinct scope: find/define/reference/caller/callee/impact layer by resolution confidence and traversal depth, while audit/audit_delta/dead_code/duplicates/perf_advice target different finding types. The only mild overlap is references_of vs callers_of and audit vs its sub-analyses, but descriptions draw explicit boundaries.

Naming Consistency3/5

There is a recognizable cluster of possessive-style names (definition_of, references_of, callers_of, callees_of, impact_of) and an audit/audit_delta pair, but the set mixes noun names (overview, endpoints, dead_code, duplicates), imperative verb_noun (find_symbol), and adjective-noun (perf_advice). The conventions are readable but not unified.

Tool Count5/5

Thirteen tools is within the well-scoped range and each covers a necessary analysis task without redundancy. The count supports a coherent workflow from orientation through navigation to audit.

Completeness5/5

The surface covers the full analysis workflow: repo overview, cross-language endpoint integrity, symbol lookup/definition/reference/caller/callee traversal, blast-radius impact, dead-code detection, full and delta audits, performance advice, and duplicate detection. No obvious dead-end or missing operation blocks the stated purpose.

Maintenance

ActivityMaintained
ResponsivenessNo issues