Embers: Tabletop RPG Toolkit

Create a session

play_create_session

Create a new session for a campaign. Required: campaignId and date (dd/mm/yy format). Other fields (name, description, planned battlemaps) are optional and pass through to play, which authorizes the caller via campaign 'contribute' permission.

Input Schema

TableJSON Schema

Name	Required	Description
`date`	Yes	Planned or actual session date in `dd/mm/yy` format. Required.
`name`	No	Session name / title.
`image`	No
`status`	No
`summary`	No	Short session summary. Max 150 characters.
`battlemaps`	No
`campaignId`	Yes	Campaign the session belongs to. Required.
`characters`	No
`description`	No	Session body / notes / recap. Markdown supported.
`sessionImages`	No

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 / battlemaps

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

addedInput schema / properties / campaignId

Added value: +{
+  "description": "Campaign the session belongs to. Required.",
+  "minLength": 1,
+  "type": "string"
+}

addedInput schema / properties / characters

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

addedInput schema / properties / date

Added value: +{
+  "description": "Planned or actual session date in `dd/mm/yy` format. Required.",
+  "pattern": "^(\\d{1,2})\\/(\\d{1,2})\\/(\\d{2})$",
+  "type": "string"
+}

addedInput schema / properties / description

Added value: +{
+  "description": "Session body / notes / recap. Markdown supported.",
+  "type": "string"
+}

addedInput schema / properties / image
```
Added value: +{
+  "type": "string"
+}
```

addedInput schema / properties / name

Added value: +{
+  "description": "Session name / title.",
+  "minLength": 1,
+  "type": "string"
+}

addedInput schema / properties / sessionImages

Added value: +{
+  "items": {
+    "additionalProperties": {},
+    "properties": {
+      "name": {
+        "type": "string"
+      },
+      "url": {
+        "type": "string"
+      },
+      "visibleToPlayers": {
+        "type": "boolean"
+      }
+    },
+    "type": "object"
+  },
+  "type": "array"
+}

addedInput schema / properties / status

Added value: +{
+  "enum": [
+    "pending",
+    "active",
+    "completed",
+    "cancelled"
+  ],
+  "type": "string"
+}

addedInput schema / properties / summary

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

addedInput schema / required

Added value: +[
+  "campaignId",
+  "date"
+]

First observedSep 21, 2026

TDQS

A4/5.0

Behavior4/5

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

The annotations are only false hints, so the description carries the behavioral burden. It adds valuable context: optional fields pass through to play and the caller must be authorized via the campaign 'contribute' permission. There is no contradiction with the annotations.

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 sentences with no filler. The create action, required inputs, optional fields, and authorization behavior are all front-loaded, and every sentence contributes useful information.

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?

The description is enough to make a basic create call and an output schema exists, but with 10 parameters and 50% schema coverage, several optional fields remain unexplained. It is minimally viable but leaves gaps around parameter meaning and alternative session operations.

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

Parameters2/5

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

Schema description coverage is only 50%, and the description does not compensate for the undocumented parameters. It names campaignId, date, name, description, and battlemaps, but leaves image, status, characters, and sessionImages unexplained. It mostly restates requiredness and date format already present in 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 opens with 'Create a new session for a campaign,' giving a specific verb and resource. The sibling list includes play_get_session, play_update_session, and play_delete_session, so the create intent is unambiguous without needing to inspect schemas.

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 clearly states the required arguments (campaignId and date), marks the rest as optional, and mentions the 'contribute' permission precondition. It does not explicitly contrast with play_update_session or play_delete_session, but the usage context for a create operation is clear.

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?