runecho
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 |
|---|---|
| structureA | Deterministic structure (files + symbols) of an enrolled repo's current code. Use to ground claims about what functions/types/exports exist. Scope with |
| diffA | Structural drift for an enrolled repo. With a+b (snapshot ids) diffs those snapshots; with |
| hashA | Deterministic root hash + file count of an enrolled repo's current code. Same code → identical hash across machines. |
| statusB | Per-repo health: last indexed, staleness, parse errors, coverage %, snapshot count, latest stored hash, file cap. |
| healthA | Store-wide health: schema version, integrity check, number of enrolled repos, db path. |
| locateA | Deterministically locate symbols in an enrolled repo: name → file:line (+ short body hash). Pass |
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 6 tools
Each tool has a clearly distinct purpose: structure for code layout, diff for changes, hash for fingerprinting, status for per-repo health, health for store-wide health, and locate for symbol resolution. There is no meaningful overlap; even structure and locate are distinct (broad structure vs. specific lookup).
All tool names are single-word, lowercase, with no underscores or mixed casing. This is perfectly consistent, even though they mix nouns and verbs. The pattern is predictable and easy to learn.
Six tools is a well-scoped set for a code analysis server. Each tool covers a distinct aspect of the domain without redundancy or bloat, and the count is within the ideal 3-15 range.
The tools cover core workflows: inspecting structure, diffing snapshots, hashing, checking health, and locating symbols. However, there is no direct way to list enrolled repositories or manage snapshots, which are minor gaps that agents may need to work around.