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). Play writes only name, summary, description, image, public, hideSections, dismissedSessionZeroNudge, xCardEnabled, and showCreatureDetails at create and ignores any other field; seats come from the invite tools. Creating it public needs Premium, VIP, or admin.

Input Schema

Name	Required	Description
`name`	Yes	Campaign name. Required.
`image`	No	Image URL. Stored as a plain string.
`public`	No	Whether non-members can see the campaign. Making the campaign public needs Premium, VIP, or admin.
`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.
`description`	No	Full campaign description. Markdown supported.
`hideSections`	No
`xCardEnabled`	No
`showCreatureDetails`	No	Whether players see a creature's details (its health and armor class, per ruleset) at the top of a token's details on the campaign's battlemaps. A battlemap shows them only when every one of its campaigns has this on. Off by default.

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 23, 2026

addedInput schema / properties / showCreatureDetails

Added value: +{
+  "description": "Whether players see a creature's details (its health and armor class, per ruleset) at the top of a token's details on the campaign's battlemaps. A battlemap shows them only when every one of its campaigns has this on. Off by default.",
+  "type": "boolean"
+}

Changed3 schema fields changedOct 15, 2026

removedInput schema / properties / active

Removed value: -{
-  "type": "boolean"
-}

changedInput schema / properties / public / description

Previous value: -"Whether non-members can see the campaign."New value: +"Whether non-members can see the campaign. Making the campaign public needs Premium, VIP, or admin."

removedInput schema / properties / sessions

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

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.5/5.0

Behavior5/5

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

Goes well beyond the annotations by listing the exact field whitelist Play persists at create time and stating that any other field is silently ignored. It also discloses the entitlement rule for `public` (Premium/VIP/admin) and the backend error semantics (400 for bad ruleset, 403 for unentitled ruleset), which annotations cannot express.

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?

Front-loads the verb, ownership, and the required parameter in the first sentence, then packs constraints and routing into the rest. Dense and mostly waste-free, though the trailing clause about the gateway letting `ruleset` be omitted is verbose relative to its value.

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?

Output schema and annotations are present, so the description only needs creation semantics, which it covers thoroughly including the field whitelist and entitlements. Minor gaps remain on the nested `hideSections` object and the undescribed `xCardEnabled` flag.

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?

Adds real meaning over the 78%-covered schema: `ruleset` is not just a tag but becomes the first leg, and the description enumerates which of the nine parameters are actually written. It does not explain `hideSections` sub-keys or `xCardEnabled`, which remain undocumented in both places.

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?

Specific verb and resource ('Create a new campaign') plus ownership scope ('owned by the calling user'). It distinguishes itself from play_update_campaign and from leg/seat operations by naming play_add_campaign_leg and the invite tools as the means to extend a campaign.

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?

Explicitly states the only required field (name) and routes follow-up work to alternatives: more legs go to play_add_campaign_leg, players go to the invite tools. It does not cover when a caller should prefer e.g. imagine_create_adventure instead, so it stops just short of full when/when-not guidance.

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?