No user-submitted related servers found.
Scored across 18 tools
Each tool targets a distinct lifecycle stage or entity, and descriptions explicitly cross-reference alternatives (e.g. check_conflicts vs publish_intent, claim_work vs start_work). Minor overlap remains among the four read tools (get_intent, get_changeset, query_work, status), but each is scoped to a different granularity. An agent can generally tell them apart.
Nearly all tools follow a clean verb_noun snake_case pattern (publish_intent, accept_changeset, resolve_conflict, register_agent, etc.). The lone deviation is 'status', a bare noun, which breaks the verb_noun convention slightly. Otherwise the set is highly predictable.
18 tools is on the heavy side but the domain is a full multi-agent coordination protocol with register, intent, claim, changeset, verification, acceptance and merge stages. Each tool maps to a distinct state transition or query, so the count is largely earned rather than padded.
The lifecycle is well covered end to end: register_agent, publish_intent, record_assessment, claim_work, start_work, publish_changeset, run_verification, accept_changeset, record_commit, plus read and conflict-resolution tools. The notable gap is messaging asymmetry: coordinate_with_agent sends messages but no MCP tool reads them, forcing recipients to the CLI.