Compounding MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| BORUNA_BIN | No | Path to the Boruna executable if Boruna is not on PATH. | |
| COMPOUNDING_WORKDIR | Yes | Path to the Git repository working directory. |
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 |
|---|---|
| swarm_initC | Create a persistent swarm with a task spec and episode budget. |
| swarm_statusB | Read state, in-flight workers, nominations, and best validated score. Votes are not correctness evidence. |
| swarm_announceC | Publish worker scope, deliverable, success condition, and abort condition before editing. |
| swarm_commitC | Record a validated contribution with parent and semantic informed_by SHAs. |
| swarm_nominateC | Nominate an existing candidate with a rationale. This records a vote, not a quality proof. |
| swarm_abstainC | Release a worker slot without spending an episode, with a non-empty reason. |
| swarm_ancestryC | Trace Git parents and informed_by dependencies from a candidate SHA in the configured repository. |
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 7 tools
Each tool targets a clearly distinct action within the swarm lifecycle: init/status manage the swarm, announce/commit/nominate/abstain handle worker contributions, and ancestry traces lineage. The descriptions explicitly distinguish similar concepts (e.g., nominate is a vote, not a quality proof; commit records a validated contribution). No overlapping purposes.
All tool names follow the same `swarm_` prefix followed by a concise snake_case verb (abstain, ancestry, init, status, announce, commit, nominate). The convention is uniform with no deviations or mixed styles.
Seven tools is well within the ideal 3-15 range and each maps to a distinct coordination operation in the swarm protocol. No tool feels redundant or out of scope for the server's stated purpose.
The surface covers the core swarm lifecycle: create a swarm, announce work, commit validated contributions, nominate candidates, abstain, trace ancestry, and read status. Minor gaps remain, such as no explicit tool to list/update/close swarms or fetch a specific candidate's full details, but these are workaroundable via status and ancestry.