ichnus2
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ICHNOS_MOCK | No | 1 for offline mock, 0 for real LLM calls. Required when a key is present. | 1 |
| GEMINI_API_KEY | No | Google Gemini API key for live mode. Set this or OPENROUTER_API_KEY to enable real LLM calls. | |
| ICHNOS_PROVIDER | No | Provider to use: 'gemini' or 'openrouter'. Inferred from whichever key exists if not set. | |
| ICHNOS_ANT_MODEL | No | Override the default cheap scout model. | |
| ICHNOS_STIGMERGY | No | 1 for trail-following (default), 0 for static ranking A/B. | 1 |
| ICHNOS_DEBUG_ANTS | No | 1 to print client and raw text for the first few ants. | 0 |
| OPENROUTER_API_KEY | No | OpenRouter API key for live mode. Set this or GEMINI_API_KEY to enable real LLM calls. | |
| ICHNOS_PROSECUTOR_MODEL | No | Optional separate model for Stage 8 verification. |
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
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| locate_bug_toolA | Locate the files most likely responsible for a bug, via a stigmergic ant-swarm search over the repo. Returns a markdown HOT/WARM/COLD heatmap with per-file evidence and, for HOT files, adversarial verification notes. This is a suggestion to prioritize reading, not a verdict -- always read the flagged files yourself before concluding. |
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 1 tool
With only one tool, there is no possibility of confusing it with another. The tool's purpose is clearly described and unambiguous.
The single tool name 'locate_bug_tool' follows a clear verb_noun pattern and is internally consistent. There are no other names to contradict it.
The server has exactly one tool, which feels thin for a typical server scope. However, the tool itself is substantial and not trivial, so it is borderline rather than severely undercounted.
The tool fully addresses its stated purpose of locating bug-related files and provides a comprehensive heatmap with evidence. There are no obvious missing operations within the narrow domain of bug localization.