Embers: Tabletop RPG Toolkit

Create a page

play_create_page

Create a new page. Required: name. Set documentType: 'player-recap' and ref: { refType: 'session', refId: <sessionId> } to make a session recap — play sends notifications to the other campaign players on recap create. Before creating a recap, call play_check_recap_exists first to avoid duplicates.

Input Schema

TableJSON Schema

Name	Required	Description
`ref`	No	What the page is attached to. Required for character notes; optional for free-form pages. Allowed on update too (Mongoose has no immutability constraint), though re-anchoring a page is unusual.
`link`	No	URL-safe slug. Lowercase letters, numbers, and hyphens only.
`name`	Yes	Page name / title. Required.
`active`	No
`public`	No
`summary`	No	Short page summary. Max 255 characters.
`keywords`	No	Comma-separated keyword string.
`promptId`	No	Mongo `_id` reference (24-character hex string).
`description`	No	Markdown body.
`documentType`	No	What kind of page this is. Defaults to 'generic'. Use 'player-recap' for a session recap.

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

addedInput schema / properties / description

Added value: +{
+  "description": "Markdown body.",
+  "type": "string"
+}

addedInput schema / properties / documentType

Added value: +{
+  "description": "What kind of page this is. Defaults to 'generic'. Use 'player-recap' for a session recap.",
+  "enum": [
+    "generic",
+    "player-recap",
+    "dm-notes",
+    "player-notes",
+    "campaign-logistics"
+  ],
+  "type": "string"
+}

addedInput schema / properties / keywords

Added value: +{
+  "description": "Comma-separated keyword string.",
+  "type": "string"
+}

addedInput schema / properties / link

Added value: +{
+  "description": "URL-safe slug. Lowercase letters, numbers, and hyphens only.",
+  "pattern": "^[a-z0-9-]+$",
+  "type": "string"
+}

addedInput schema / properties / name

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

addedInput schema / properties / promptId

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

addedInput schema / properties / public
```
Added value: +{
+  "type": "boolean"
+}
```

addedInput schema / properties / ref

Added value: +{
+  "additionalProperties": {},
+  "description": "What the page is attached to. Required for character notes; optional for free-form pages. Allowed on update too (Mongoose has no immutability constraint), though re-anchoring a page is unusual.",
+  "properties": {
+    "refId": {
+      "minLength": 1,
+      "type": "string"
+    },
+    "refType": {
+      "enum": [
+        "campaign",
+        "session",
+        "character"
+      ],
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

addedInput schema / properties / summary

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

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

First observedSep 21, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Beyond the annotations, the description discloses a notable side effect: creating a player-recap sends notifications to the other campaign players. It also warns about duplicate recaps, which is valuable non-obvious behavior for a create operation.

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 three tight sentences with no filler. The required field is front-loaded, the recap configuration is given next, and the duplicate-check warning closes it; every sentence earns its place.

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?

Given a rich schema, an output schema, and annotations that already signal mutability and open-world behavior, this description covers the main creation path and the special recap path. The only meaningful operation-specific guidance an agent needs is the duplicate check, which is included.

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?

With 80% schema coverage, the schema already handles most parameter meaning. The description adds essential cross-parameter semantics by explaining that documentType: 'player-recap' plus ref { refType: 'session', refId: <sessionId> } triggers the recap notification behavior, which the schema alone does not convey.

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 page', a specific verb and resource, and clearly distinguishes this creation tool from siblings like play_update_page and play_delete_page. It further sharpens purpose by explaining the session-recap creation path.

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 gives explicit guidance for the recap use case: set documentType and ref, and call play_check_recap_exists first to avoid duplicates. It does not explicitly contrast with play_update_page, but the create-vs-update distinction is strongly implied and the recap workflow is well covered.

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?