Embers: Tabletop RPG Toolkit

Create a move

play_create_move

Record a new play-by-email move on a campaign. Required: campaignId. Optional: name (defaults 'Move '), number (defaults next-in-sequence), date dd/mm/yy (defaults today), description, sessionId (chapter), parentId (child scene; excludes sessionId), playerIds (visibility restriction to listed campaign players). GM-only: caller must be the campaign owner or an accepted gamemaster.

Input Schema

TableJSON Schema

Name	Required	Description
`date`	No	Move date in `dd/mm/yy` format. Defaults to today on create. Play parses this server-side on both create and update.
`name`	No	Move name / title (e.g. 'Move 185', 'Interlude 12'). Defaults to 'Move <number>' when omitted on create.
`number`	No	Game label number. Non-unique (parallel scenes share one). Defaults to the campaign's high-water + 1 on create. Display position is `order`, not this.
`parentId`	No	Parent move, making this a child scene (split party). Same campaign only, one level deep (a child cannot be a parent; a move with children cannot become a child). Children render on the parent's page, stay out of the feed and chapter lists, and cannot carry a sessionId. Pass null to detach back into the feed.
`playerIds`	No	Visibility restriction: user ids from the campaign's player roster. Empty/omitted = visible to every campaign participant. When set, the move is invisible to players not listed (dropped from lists, 404 on read); the GM always sees it. Pass [] on update to reopen the move to everyone.
`sessionId`	No	Chapter session to group this move under. Must belong to the same campaign. Pass null to detach the move back to the unchaptered feed.
`campaignId`	Yes	Campaign the move belongs to. Required. Caller must be the campaign owner or an accepted gamemaster.
`description`	No	The collated round: GM narration, player contributions, rolls. Markdown supported.

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed11 schema fields changedSep 25, 2026

addedInput schema / $schema

Added value: +"http://json-schema.org/draft-07/schema#"

addedInput schema / additionalProperties
```
Added value: +{}
```

addedInput schema / properties / campaignId

Added value: +{
+  "description": "Campaign the move belongs to. Required. Caller must be the campaign owner or an accepted gamemaster.",
+  "minLength": 1,
+  "type": "string"
+}

addedInput schema / properties / date

Added value: +{
+  "description": "Move date in `dd/mm/yy` format. Defaults to today on create. Play parses this server-side on both create and update.",
+  "pattern": "^(\\d{1,2})\\/(\\d{1,2})\\/(\\d{2})$",
+  "type": "string"
+}

addedInput schema / properties / description

Added value: +{
+  "description": "The collated round: GM narration, player contributions, rolls. Markdown supported.",
+  "type": "string"
+}

addedInput schema / properties / name

Added value: +{
+  "description": "Move name / title (e.g. 'Move 185', 'Interlude 12'). Defaults to 'Move <number>' when omitted on create.",
+  "minLength": 1,
+  "type": "string"
+}

addedInput schema / properties / number

Added value: +{
+  "description": "Game label number. Non-unique (parallel scenes share one). Defaults to the campaign's high-water + 1 on create. Display position is `order`, not this.",
+  "exclusiveMinimum": 0,
+  "maximum": 9007199254740991,
+  "type": "integer"
+}

addedInput schema / properties / parentId

Added value: +{
+  "anyOf": [
+    {
+      "minLength": 1,
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "description": "Parent move, making this a child scene (split party). Same campaign only, one level deep (a child cannot be a parent; a move with children cannot become a child). Children render on the parent's page, stay out of the feed and chapter lists, and cannot carry a sessionId. Pass null to detach back into the feed."
+}

addedInput schema / properties / playerIds

Added value: +{
+  "description": "Visibility restriction: user ids from the campaign's player roster. Empty/omitted = visible to every campaign participant. When set, the move is invisible to players not listed (dropped from lists, 404 on read); the GM always sees it. Pass [] on update to reopen the move to everyone.",
+  "items": {
+    "minLength": 1,
+    "type": "string"
+  },
+  "type": "array"
+}

addedInput schema / properties / sessionId

Added value: +{
+  "anyOf": [
+    {
+      "minLength": 1,
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "description": "Chapter session to group this move under. Must belong to the same campaign. Pass null to detach the move back to the unchaptered feed."
+}

addedInput schema / required
```
Added value: +[
+  "campaignId"
+]
```

First observedSep 21, 2026

TDQS

A4.3/5.0

Behavior4/5

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

The annotations provide only false hints, so the description carries most of the behavioral disclosure burden. It does so well by revealing the GM-only requirement, defaulting behavior for name/number/date, and visibility restrictions via playerIds. It does not describe the response shape, but an output schema exists, and the description does not contradict any annotation.

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?

The description is compact and well organized: a one-line purpose, then required vs. optional parameters, then the GM-only constraint. Every sentence earns its place, and the core action is front-loaded. There is no filler or redundancy.

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

Completeness5/5

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

For an 8-parameter creation tool, the description together with the fully covered schema and output schema gives an agent everything needed to call it correctly: required campaignId, default behaviors, key constraints, and authorization. Nothing essential is missing.

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 100%, with detailed parameter explanations already present, so the baseline is 3. The description condenses important information such as 'parentId (child scene; excludes sessionId)' and 'playerIds (visibility restriction)', but it mostly mirrors the schema rather than adding new semantic meaning. It is useful for quick scanning but does not materially extend the schema.

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

Purpose5/5

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

The description states a specific verb and resource: 'Record a new play-by-email move on a campaign.' This clearly distinguishes it from sibling tools like play_create_session or play_create_page, and the PBEM qualifier makes the domain explicit. Even without reading the schema, an agent knows exactly what artifact this tool creates.

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

Usage Guidelines4/5

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

The description provides clear context for when to use the tool: creating a new move, with campaignId required. It also gives an important exclusion (parentId excludes sessionId) and a caller restriction (GM-only: campaign owner or accepted gamemaster). However, it does not explicitly name alternatives such as play_update_move for editing existing moves, so it falls just short of the top bar.

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

All Embers: Tabletop RPG Toolkit tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?