Embers: Tabletop RPG Toolkit

Create a play campaign

play_create_campaign

Create a new campaign owned by the calling user. Required: name. ruleset becomes the campaign's first leg (campaigns hold ruleset-specific material in per-ruleset legs; add more with play_add_campaign_leg). Other fields (summary, description, settings) pass through to play, which validates the payload.

Input Schema

TableJSON Schema

Name	Required	Description
`name`	Yes	Campaign name. Required.
`image`	No	Image URL. Stored as a plain string.
`active`	No
`public`	No	Whether non-members can see the campaign.
`ruleset`	No	Ruleset code; list_rulesets returns the codes this account can use. Becomes the campaign's first leg. Play enforces required and a known code on the backend (400) and answers 403 for a ruleset this account is not entitled to; the gateway lets it be omitted so the LLM gets a clean backend error if it forgets.
`summary`	No	Short campaign summary. Max 150 characters.
`sessions`	No
`description`	No	Full campaign description. Markdown supported.
`hideSections`	No
`xCardEnabled`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedSep 27, 2026

changedInput schema / properties / ruleset / description

Previous value: -"Ruleset code (e.g. '5th Edition', '5e24', 'PFRPG', 'Savage Worlds'). Becomes the campaign's first leg. Play enforces required on the backend; the gateway lets it be omitted so the LLM gets a clean backend error if it forgets."New value: +"Ruleset code; list_rulesets returns the codes this account can use. Becomes the campaign's first leg. Play enforces required and a known code on the backend (400) and answers 403 for a ruleset this account is not entitled to; the gateway lets it be omitted so the LLM gets a clean backend error if it forgets."

removedInput schema / properties / ruleset / enum

Removed value: -[
-  "5th Edition",
-  "5e24",
-  "PFRPG",
-  "PFRPG2",
-  "PF Playtest",
-  "Savage Worlds",
-  "Savage Embers",
-  "Solarian Conflict",
-  "Embers RPG",
-  "Universal",
-  "Fate Core",
-  "Fate Accelerated"
-]

addedInput schema / properties / ruleset / minLength
```
Added value: +1
```

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 / active
```
Added value: +{
+  "type": "boolean"
+}
```

addedInput schema / properties / description

Added value: +{
+  "description": "Full campaign description. Markdown supported.",
+  "type": "string"
+}

addedInput schema / properties / hideSections

Added value: +{
+  "additionalProperties": {},
+  "properties": {
+    "characters": {
+      "type": "boolean"
+    },
+    "logistics": {
+      "type": "boolean"
+    },
+    "players": {
+      "type": "boolean"
+    },
+    "rules": {
+      "type": "boolean"
+    },
+    "safetyTools": {
+      "type": "boolean"
+    },
+    "sessionZero": {
+      "type": "boolean"
+    },
+    "sessions": {
+      "type": "boolean"
+    }
+  },
+  "type": "object"
+}

addedInput schema / properties / image

Added value: +{
+  "description": "Image URL. Stored as a plain string.",
+  "type": "string"
+}

addedInput schema / properties / name

Added value: +{
+  "description": "Campaign name. Required.",
+  "minLength": 1,
+  "type": "string"
+}

addedInput schema / properties / public

Added value: +{
+  "description": "Whether non-members can see the campaign.",
+  "type": "boolean"
+}

addedInput schema / properties / ruleset

Added value: +{
+  "description": "Ruleset code (e.g. '5th Edition', '5e24', 'PFRPG', 'Savage Worlds'). Becomes the campaign's first leg. Play enforces required on the backend; the gateway lets it be omitted so the LLM gets a clean backend error if it forgets.",
+  "enum": [
+    "5th Edition",
+    "5e24",
+    "PFRPG",
+    "PFRPG2",
+    "PF Playtest",
+    "Savage Worlds",
+    "Savage Embers",
+    "Solarian Conflict",
+    "Embers RPG",
+    "Universal",
+    "Fate Core",
+    "Fate Accelerated"
+  ],
+  "type": "string"
+}

addedInput schema / properties / sessions

Added value: +{
+  "items": {
+    "description": "Mongo `_id` reference (24-character hex string).",
+    "minLength": 1,
+    "type": "string"
+  },
+  "type": "array"
+}

addedInput schema / properties / summary

Added value: +{
+  "description": "Short campaign summary. Max 150 characters.",
+  "maxLength": 150,
+  "type": "string"
+}

addedInput schema / properties / xCardEnabled
```
Added value: +{
+  "type": "boolean"
+}
```
addedInput schema / required
```
Added value: +[
+  "name"
+]
```

First observedSep 21, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare this as a non-read-only, non-idempotent, non-destructive, open-world write. The description adds meaningful specifics beyond that: ownership semantics, that 'ruleset' is materialized as a leg, and that Play validates the payload (400 for missing/unknown ruleset, 403 for unentitled ruleset). It does not cover reversibility or rate limits, so it stops short of the top score.

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 tight sentences, front-loaded with the operation and the required field, then the leg/validation detail. Slightly dense in the middle clause about legs, but no filler.

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

Completeness4/5

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

For a 10-parameter creation tool, it covers purpose, required field, the non-obvious leg mechanic, and backend failure modes, while an output schema exists so return values need no prose. Annotations carry the safety profile. Only unusual params like hideSections/xCardEnabled are left to the schema.

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 description coverage is 60%, so the schema documents about half the parameters. The description compensates by explaining the pass-through contract for summary/description/settings and the leg behavior plus backend error codes for ruleset, adding real meaning beyond the schema text.

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?

States a specific verb and resource ('Create a new campaign') plus scope ('owned by the calling user'), which cleanly separates it from play_update_campaign, play_delete_campaign, and the imagine_create_* siblings. An agent can identify the operation without opening the schema.

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?

Explains the setup context: required 'name', and that 'ruleset' becomes the campaign's first leg with more legs added via play_add_campaign_leg. It names the follow-up tool but does not state exclusions or when a different creation path (e.g. imagine_create_adventure) would be preferred.

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?