Ennodia
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ENNODIA_HISTORY | No | Set to 0 to disable terminal run history storage. If not set, history is stored locally. | 1 |
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": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| ennodia_list_harnessesA | Discover local harnesses, availability, versions, capabilities, adapter notes, and inputGuidance. Before audio/image/video work, read inputGuidance: model capabilities do not guarantee native input through a harness. Use first when setup or routing fails. |
| ennodia_list_skillsA | Discover prompt-only skills from project, user, and built-in skill directories without returning full instruction text. |
| ennodia_runA | Start a high-level Ennodia orchestration. Set pragmatic for evidence-focused investigation or patch proposals with one or more independent workers. Use Plan Advisor for tailored model and skill assignments. Use this as the default entrypoint: it plans routing, starts one or more local harness tasks, optionally compares successful outputs, and returns a run ID. Runs usually take minutes; use ennodia_get_run with waitMs: 30000 and includeEvents: false until terminal, then consume and verify its answer. A wait timeout does not cancel or finish the run. |
| ennodia_historyA | Read terminal run receipts persisted under the local Ennodia history directory. Use after a restart to inspect previous final answers and Judge disagreement analysis. |
| ennodia_get_runA | Inspect a run or wait up to waitMs for completion. Prefer waitMs: 30000, compact: true and includeEvents: false while awaiting results. A nonterminal response means work continues; do not claim its findings were consumed. |
| ennodia_cancel_runA | Cancel a high-level run and any active child task, Judge, or Result Advisor. |
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 distinct lifecycle role: list_harnesses/list_skills are discovery, run starts work, get_run reads status, history reads past receipts, cancel_run stops work. The only mild overlap is get_run vs history (live vs persisted) and run vs list_harnesses routing guidance, but descriptions clarify these boundaries.
All tools use the ennodia_ prefix with snake_case verb_noun naming, which is highly consistent. Minor deviation: ennodia_run is a bare verb with no noun, while others include an object (enumodia_list_harnesses, ennodia_get_run).
Six tools is well-scoped for an orchestration server, covering discovery, execution, polling, history, and cancellation without redundancy. Each tool earns its place in the run lifecycle.
The lifecycle is well covered: discover harnesses/skills, start run, poll, cancel, and read history. Minor gap: no explicit tool for listing or retrieving an in-progress run's result beyond polling, but get_run with waitMs handles terminal results adequately.