mimry
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| NO_COLOR | No | Set to 1 to turn off colour output. | |
| MIMRY_LOCK_TIMEOUT_SECONDS | No | Lock waits are bounded to 10 seconds by default; set MIMRY_LOCK_TIMEOUT_SECONDS to raise the bound. |
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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| mimry_statusB | Return MIMRY initialization and index freshness for a root. Freshness trusts unchanged file metadata, like git; |
| mimry_preflightD | Fast readiness check and task context, matching CLI preflight. |
| mimry_findC | Search files, optionally with bounded live-source snippets. Pass offset=0 on page one. |
| mimry_relatedC | Return files related to a query by graph-aware ranking. |
| mimry_symbolA | Search indexed symbols by name, falling back to file names. Set relations to "callers" (what calls the symbol) or "callees" (what it calls), with depth 1 to 3 for how many calls away to follow. file picks one symbol when several share the name, and file may end in ":N" to pick by line; line picks the symbol that starts on that line, or else spans it. Without relations this only searches. |
| mimry_pathC | Find a relationship path between two files/symbols/queries. |
| mimry_impactA | What a change touches: callers, importers and tests to run. target is a symbol name (file picks one when several share it, and line picks by the line it starts on or spans) or a repo-relative file path. changed=True uses the working tree against HEAD instead. depth is 1 to 5, how many calls back to follow. |
| mimry_whyC | Explain why a file or symbol ranked for a task query. |
| mimry_feedbackC | Record local agent usage feedback for future ranking. |
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
Most tools have distinct purposes (impact=change effects, path=relationship route, why=ranking explanation, feedback=telemetry), but there is mild overlap between mimry_preflight and mimry_status (both readiness/state checks) and between mimry_find and mimry_related (both return files for a query). The descriptions largely disambiguate these, but an agent could still hesitate on which readiness or file-retrieval call to pick.
All tools share a uniform mimry_ prefix and single lowercase word style, which is predictable and readable. However the words mix nouns (impact, path, status, symbol) and verbs (find, why, feedback), so it is consistent in form but not a strict verb_noun pattern.
Nine tools is well-scoped for a code-graph/search server, with each tool covering a distinct facet (search, symbols, relationships, impact, status, feedback). No filler or redundant entries.
The surface covers search, symbol lookup, graph relationships, change impact, ranking explanation, and readiness/freshness well. The one notable gap is a dedicated index build/reindex operation, since status/preflight only report freshness rather than triggering indexing.