Branchwright MCP

create_campaign

Idempotent

Start a new campaign from a bundled template or a supplied JSON world pack. Reuse the creation key on retries to avoid duplicates.

Instructions

Create an independent campaign from a bundled template or a supplied JSON world pack. Reuse the creation key on retries.

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": {
      "name": "<name>",
      "idempotency_key": "<idempotency_key>"
    },
    "name": "create_campaign"
  }
}

Input Schema

Name	Required	Description	Default
`name`	Yes
`world`	No
`template`	No
`idempotency_key`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.3.0Oct 18, 2026

TDQS

A3.5/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, and idempotentHint=true, so safety and idempotency are covered. The description's 'Reuse the creation key on retries' restates idempotency rather than adding new behavior, and adds nothing about auth/permissions or what happens to an existing campaign with the same name.

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

Conciseness5/5

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

Two short sentences, front-loaded with the core action, and the retry note placed last. No filler, every clause carries meaning.

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

Completeness3/5

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

Given a complex nested world schema, no output schema, and 0% parameter description coverage, the description is thinner than the tool's complexity warrants. It conveys the high-level action but omits mode exclusivity rules, template semantics, and the shape of a supplied world pack.

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

Parameters3/5

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

Schema description coverage is 0%, so the description must compensate and does so only partially: 'bundled template' maps to the template enum, 'JSON world pack' to the world object, and 'creation key' to idempotency_key. The required 'name' parameter and the deep world structure (genre, rules, actors, events) are never explained.

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?

The description states a specific verb (create) and resource (campaign) and clarifies that it operates from a bundled template OR a supplied JSON world pack, which distinguishes it from read-oriented siblings like list_campaigns. It does not name a sibling explicitly, but the scope is unambiguous.

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?

The phrase 'from a bundled template or a supplied JSON world pack' implies the two mutually exclusive creation modes (the template enum vs. the world object), and 'Reuse the creation key on retries' gives retry guidance. However, it never states when to choose this tool over create_branch or when prerequisites apply, leaving usage to inference.

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

Deploy Server