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

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. Setting or changing a page link needs Premium, VIP, or admin.
`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

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 15, 2026

changedInput schema / properties / link / description

Previous value: -"URL-safe slug. Lowercase letters, numbers, and hyphens only."New value: +"URL-safe slug. Lowercase letters, numbers, and hyphens only. Setting or changing a page link needs Premium, VIP, or admin."

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

Behavior4/5

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

Annotations already cover the write/non-idempotent/non-destructive profile, and the description adds a genuine side effect not in structured fields: play sends notifications to other campaign players when a recap is created. It also discloses the duplicate-avoidance requirement. It omits permission requirements (the schema, not the description, notes link changes need Premium/VIP/admin).

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?

Three sentences, zero filler, and the required parameter is front-loaded before the recap recipe and the prerequisite check. Every sentence carries actionable content.

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?

An output schema exists, so return values need no explanation, and the description covers the required param, the primary recap workflow, the side effect, and the prerequisite call. Given 10 parameters and a permission-gated link field, a bit more on permissions/constraints would make it fully 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 coverage is 80%, so the baseline is 3; the description earns above that by showing how name, documentType, and the nested ref object (refType: 'session', refId) combine into a working recap call, which the schema documents only field-by-field. It does not touch the remaining optional params (public, link, keywords), but those are reasonably covered by schema text.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/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 page') and immediately narrows into a concrete sub-case (session recap via documentType/ref). It is clear what the tool does, but it does not explicitly distinguish itself from the many sibling create tools (imagine_create_adventure_page, play_create_session, etc.) sharing the same verb.

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?

Gives a real usage condition (set documentType: 'player-recap' plus ref to make a recap) and an explicit prerequisite: call play_check_recap_exists first to avoid duplicates. It names the alternative instead of leaving routing to inference, though it never states when a page should not be created or how it relates to play_update_page.

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?