Branchwright MCP

commit_turn

Idempotent

Atomically validate and commit an authorized scene to the campaign timeline, preserving idempotency keys on retries so only a committed receipt confirms success.

Instructions

Atomically validate and commit the authorized scene. Preserve exact arguments/key on an unconfirmed retry. Only a committed receipt means success.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "campaign_id": "<campaign_id>",
      "branch_id": "<branch_id>",
      "expected_revision": "<expected_revision>",
      "preparation_id": "<preparation_id>",
      "player_action": "<player_action>",
      "policy_sha256": "<policy_sha256>",
      "idempotency_key": "<idempotency_key>",
      "narration": "<narration>",
      "summary": "<summary>",
      "outcome": "<outcome>"
    },
    "name": "commit_turn"
  }
}

Input Schema

Name	Required	Description	Default
`changes`	No
`outcome`	Yes
`summary`	Yes
`branch_id`	Yes
`narration`	Yes
`campaign_id`	Yes
`fact_updates`	No
`check_results`	No
`player_action`	Yes
`policy_sha256`	Yes
`preparation_id`	Yes
`idempotency_key`	Yes
`expected_revision`	Yes
`knowledge_updates`	No
`check_context_sha256`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.3.0Oct 18, 2026

TDQS

B3.3/5.0

Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations cover the safety profile (idempotentHint=true, readOnlyHint=false), but the description adds real value beyond them: atomicity, the requirement to reuse exact arguments and key on an unconfirmed retry, and that only a committed receipt proves success. It stops short of describing auth/permission needs or what an uncommitted retry returns.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three short, front-loaded sentences with no filler; the commit/atomicity point leads. Slight terseness given the tool's complexity, but every sentence earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 15-parameter, 10-required tool with nested objects, 0% schema coverage, and no output schema, this description is far too thin. It omits any guidance on the payload structure, revision/precondition semantics, or what the receipt contains, leaving large gaps an agent cannot fill from structured data.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% across 15 parameters, so the description carries full burden, yet it only vaguely references 'arguments/key' (likely idempotency_key). It adds essentially no meaning for expected_revision, policy_sha256, preparation_id, outcome, changes, or the other structured fields.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb (commit) and resource (the authorized scene), and pairing it against the sibling prepare_turn is implicit but inferable. It clearly signals this is the finalization step, though it never names prepare_turn or other siblings explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Implied usage is present: 'Only a committed receipt means success' tells the agent this is the terminal commit step, and the retry note establishes retry conditions. However, there is no explicit when/when-not or named alternative (e.g. prepare_turn must precede it), so an agent must infer the workflow ordering.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server