Embers: Tabletop RPG Toolkit

Update a move

play_update_move

Idempotent

Update a move by id: name, description, number (game label), date, order (shelf position), sessionId (chapter; null detaches), parentId (child scene; null detaches; setting it clears the chapter), or playerIds (visibility; [] reopens to everyone). Only supplied fields are sent. GM-only. REQUIRES baseUpdatedAt: copy updatedAt from a fresh play_get_move read; a stale or fabricated value is rejected with OUT_OF_SYNC and nothing is written.

Input Schema

TableJSON Schema

Name	Required	Description
`id`	Yes	Mongo `_id` of the move to update.
`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.
`order`	No	Shelf position within the campaign (the feed's only sort key; GM drag-reordering rewrites it). Positive integer.
`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.
`description`	No	The collated round: GM narration, player contributions, rolls. Markdown supported.
`baseUpdatedAt`	Yes	REQUIRED proof that you are working from the latest version: copy the `updatedAt` value verbatim from a FRESH read of this exact record (use the matching get tool first). Values from memory, from an earlier conversation, or guessed timestamps are rejected with OUT_OF_SYNC and nothing is written. After a successful update, the response carries the new `updatedAt` — use that for any follow-up write.

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed13 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 / baseUpdatedAt

Added value: +{
+  "description": "REQUIRED proof that you are working from the latest version: copy the `updatedAt` value verbatim from a FRESH read of this exact record (use the matching get tool first). Values from memory, from an earlier conversation, or guessed timestamps are rejected with OUT_OF_SYNC and nothing is written. After a successful update, the response carries the new `updatedAt` — use that for any follow-up write.",
+  "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 / id

Added value: +{
+  "description": "Mongo `_id` of the move to update.",
+  "minLength": 1,
+  "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 / order

Added value: +{
+  "description": "Shelf position within the campaign (the feed's only sort key; GM drag-reordering rewrites it). Positive integer.",
+  "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: +[
+  "id",
+  "baseUpdatedAt"
+]

First observedSep 21, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Annotations declare readOnlyHint=false, idempotentHint=true, destructiveHint=false. The description adds substantial context: partial-update semantics ('Only supplied fields are sent'), optimistic concurrency requirement, GM-only access, and side effects of null values like 'null detaches' and 'setting it clears the chapter'. This exceeds what annotations convey.

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?

The description is one dense but well-organized paragraph that front-loads the supported fields and places the critical concurrency warning prominently. It is compact for 10 parameters. A line break before the baseUpdatedAt warning would improve scannability, but every sentence is necessary and non-redundant.

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 a complex 10-parameter mutation tool, the description covers update semantics, required precondition (fresh read), failure mode, GM restriction, and field-level dependencies. The output schema exists, so return-value details need not be spelled out. Highly complete.

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

Parameters4/5

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

Schema covers 100% of parameters with rich descriptions, so the description need not repeat them. The description adds semantic gloss: 'null detaches', '[] reopens to everyone', 'sessionId (chapter; null detaches)', and the critical baseUpdatedAt provenance rule. Given the schema already documents each parameter, a 4 is appropriate.

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: 'Update a move by id', then enumerates all mutable fields and their semantics. It distinguishes from siblings like play_create_move and play_delete_move by being explicitly an update. The title and description align, and the resource (move) is clearly differentiated from page/session/campaign tools.

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

Usage Guidelines5/5

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

The description provides strong usage guidance: it lists only-supplied-fields-are-sent behavior, states GM-only requirement, and explicitly instructs the agent to copy baseUpdatedAt from a fresh play_get_move read. It warns against stale or fabricated values and explains the OUT_OF_SYNC failure mode. This gives clear when-to-use context against sibling read tools.

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?