Embers: Tabletop RPG Toolkit

Create an adventure page

imagine_create_adventure_page

Create a new page inside an adventure. Required: adventureId, name. Use this for scene descriptions, encounter rooms, NPC profiles, plot beats. Valid documentType values: generic, act, scene, location, character, handout, lore, appendix, map. Items and rules are NOT page types; author them in vault and reference them, not as adventure pages. Set the tags array so the page is filterable in adventure-page listings; the page's documentType is also auto-added to the searchable keyword set.

Input Schema

TableJSON Schema

Name	Required	Description
`map`	No	Location shape: Mongo `_id` of the Map this location belongs to. Pass null to clear.
`goal`	No
`link`	No	URL-safe slug. Lowercase letters, numbers, hyphens, slashes.
`name`	Yes	Page name. Required.
`tags`	No	Tag list. Imagine stores as a comma-separated `keywords` string.
`image`	No
`active`	No
`mapPin`	No
`aliases`	No
`content`	No	Page body in markdown. Imagine renders this verbatim. WARNING: REPLACED wholesale on update; prefer imagine_replace_in_adventure_page for surgical edits.
`details`	No	Label/value list of arbitrary metadata pairs.
`summary`	No	Short page summary. Max 150 characters (matches the AdventurePage Mongoose schema's maxlength). Sibling Adventure and WorldPage summaries share the same cap; legacy World summaries cap at 255 (cross-app convention).
`duration`	No
`parentId`	No	Mongo `_id` of the parent page (for tree structure).
`template`	No	Template id when authored from a template.
`menuOrder`	No
`vaultRefs`	No	Participants on the page. Each entry `{ vaultId?, type?, count?, name? }`.
`adventureId`	Yes	Adventure to add the page to.
`locationKey`	No
`documentType`	No	Structural type. Drives shape-specific fields.
`treasureRefs`	No	Treasure entries. Same shape as `vaultRefs`.
`outboundLinks`	No	AdventurePage ids this page links to. Imagine recomputes this on save when missing; explicit values override.
`relationships`	No	Sibling AdventurePage ids the page relates to.
`worldPageRefs`	No	Mongo `_id` list of referenced world pages.

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed27 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 / adventureId

Added value: +{
+  "description": "Adventure to add the page to.",
+  "minLength": 1,
+  "type": "string"
+}

addedInput schema / properties / aliases

Added value: +{
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

addedInput schema / properties / content

Added value: +{
+  "description": "Page body in markdown. Imagine renders this verbatim. WARNING: REPLACED wholesale on update; prefer imagine_replace_in_adventure_page for surgical edits.",
+  "type": "string"
+}

addedInput schema / properties / details

Added value: +{
+  "description": "Label/value list of arbitrary metadata pairs.",
+  "items": {
+    "additionalProperties": {},
+    "properties": {
+      "label": {
+        "type": "string"
+      },
+      "value": {
+        "type": "string"
+      }
+    },
+    "type": "object"
+  },
+  "type": "array"
+}

addedInput schema / properties / documentType

Added value: +{
+  "description": "Structural type. Drives shape-specific fields.",
+  "enum": [
+    "generic",
+    "act",
+    "scene",
+    "location",
+    "character",
+    "handout",
+    "lore",
+    "appendix",
+    "map"
+  ],
+  "type": "string"
+}

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

addedInput schema / properties / link

Added value: +{
+  "description": "URL-safe slug. Lowercase letters, numbers, hyphens, slashes.",
+  "type": "string"
+}

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

addedInput schema / properties / map

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "description": "Location shape: Mongo `_id` of the Map this location belongs to. Pass null to clear."
+}

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

addedInput schema / properties / menuOrder

Added value: +{
+  "maximum": 9007199254740991,
+  "minimum": -9007199254740991,
+  "type": "integer"
+}

addedInput schema / properties / name

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

addedInput schema / properties / outboundLinks

Added value: +{
+  "description": "AdventurePage ids this page links to. Imagine recomputes this on save when missing; explicit values override.",
+  "items": {
+    "description": "Mongo `_id` reference (24-character hex string).",
+    "minLength": 1,
+    "type": "string"
+  },
+  "type": "array"
+}

addedInput schema / properties / parentId

Added value: +{
+  "description": "Mongo `_id` of the parent page (for tree structure).",
+  "type": "string"
+}

addedInput schema / properties / relationships

Added value: +{
+  "description": "Sibling AdventurePage ids the page relates to.",
+  "items": {
+    "description": "Mongo `_id` reference (24-character hex string).",
+    "minLength": 1,
+    "type": "string"
+  },
+  "type": "array"
+}

addedInput schema / properties / summary

Added value: +{
+  "description": "Short page summary. Max 150 characters (matches the AdventurePage Mongoose schema's maxlength). Sibling Adventure and WorldPage summaries share the same cap; legacy World summaries cap at 255 (cross-app convention).",
+  "maxLength": 150,
+  "type": "string"
+}

addedInput schema / properties / tags

Added value: +{
+  "description": "Tag list. Imagine stores as a comma-separated `keywords` string.",
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

addedInput schema / properties / template

Added value: +{
+  "description": "Template id when authored from a template.",
+  "type": "string"
+}

addedInput schema / properties / treasureRefs

Added value: +{
+  "description": "Treasure entries. Same shape as `vaultRefs`.",
+  "items": {
+    "additionalProperties": {},
+    "properties": {
+      "count": {
+        "type": "number"
+      },
+      "name": {
+        "type": "string"
+      },
+      "type": {
+        "type": "string"
+      },
+      "vaultId": {
+        "type": "string"
+      }
+    },
+    "type": "object"
+  },
+  "type": "array"
+}

addedInput schema / properties / vaultRefs

Added value: +{
+  "description": "Participants on the page. Each entry `{ vaultId?, type?, count?, name? }`.",
+  "items": {
+    "additionalProperties": {},
+    "properties": {
+      "count": {
+        "type": "number"
+      },
+      "name": {
+        "type": "string"
+      },
+      "type": {
+        "type": "string"
+      },
+      "vaultId": {
+        "type": "string"
+      }
+    },
+    "type": "object"
+  },
+  "type": "array"
+}

addedInput schema / properties / worldPageRefs

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

addedInput schema / required

Added value: +[
+  "adventureId",
+  "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 establish this as a mutating, non-idempotent, non-destructive operation, and the description adds behavioral nuance beyond that: 'Set the tags array so the page is filterable' and 'documentType is also auto-added to the searchable keyword set.' It does not contradict any annotation.

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?

The description is front-loaded with the core action and required fields, and most sentences earn their place by adding use cases or exclusions. The only mild redundancy is restating the documentType enum that already exists in the input schema, but it remains compact and scannable.

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 24-parameter create tool, the description covers the essentials: required fields, permitted document types, non-goals, and tag/filter behavior. The output schema covers return values and the input schema documents most optional fields, so an agent can safely select and invoke the tool; a minor gap is that omitting documentType is not addressed.

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

Parameters3/5

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

The schema covers 67% of parameters, and the description adds useful semantics for the most decision-critical ones: required adventureId/name, the valid documentType enum, and tag filtering behavior. However, it does not compensate for the several schema-undocumented optional fields such as goal, mapPin, locationKey, aliases, and menuOrder.

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 leads with a specific verb and resource: 'Create a new page inside an adventure.' It reinforces scope with concrete use cases ('scene descriptions, encounter rooms, NPC profiles, plot beats') and clearly distinguishes itself from vault item/rule creation tools by stating those are NOT page types.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explicitly says when to use the tool and gives an exclusion with routing guidance: 'Items and rules are NOT page types; author them in vault and reference them, not as adventure pages.' This tells an agent both what this tool is for and when to choose an alternative.

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?