Embers: Tabletop RPG Toolkit

Create an adventure

imagine_create_adventure

Create a new adventure owned by the calling user. Required: name and ruleset (imagine has no app-wide ruleset default for adventures). Other fields pass through to imagine.

Input Schema

TableJSON Schema

Name	Required	Description
`link`	No	URL-safe slug. Lowercase letters, numbers, and hyphens. Imagine auto-suggests at create time when omitted.
`name`	Yes	Adventure name. Required.
`image`	No	Header image URL.
`level`	No	Recommended character level range. Each side optional; null means unset.
`world`	No	Optional World _id this adventure belongs to.
`active`	No
`public`	No
`status`	No
`ruleset`	Yes	Ruleset code. Required at create time; imagine has no default ruleset for adventures.
`summary`	No	Short summary; capped at 150 characters by imagine.
`version`	No
`keywords`	No	Comma-separated keyword string used by adventure-wide tag/search.
`barImages`	No	GM-curated reference images displayed in a fixed bar across the adventure (maps, handouts, NPC portraits).
`partySize`	No	Recommended party size range.
`publisher`	No
`companions`	No
`description`	No	Full adventure description. Markdown supported.
`imageCarousel`	No
`estimatedHours`	No
`contentWarnings`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed23 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 / barImages

Added value: +{
+  "description": "GM-curated reference images displayed in a fixed bar across the adventure (maps, handouts, NPC portraits).",
+  "items": {
+    "additionalProperties": {},
+    "properties": {
+      "name": {
+        "type": "string"
+      },
+      "url": {
+        "description": "Image URL. Required by Mongoose; gateway leaves it optional so a missing url surfaces as a clean backend error.",
+        "type": "string"
+      }
+    },
+    "type": "object"
+  },
+  "type": "array"
+}

addedInput schema / properties / companions

Added value: +{
+  "items": {
+    "additionalProperties": {},
+    "properties": {
+      "name": {
+        "type": "string"
+      },
+      "type": {
+        "type": "string"
+      },
+      "vaultId": {
+        "description": "Vault entity id (character/monster). Required by Mongoose.",
+        "type": "string"
+      }
+    },
+    "type": "object"
+  },
+  "type": "array"
+}

addedInput schema / properties / contentWarnings

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

addedInput schema / properties / description

Added value: +{
+  "description": "Full adventure description. Markdown supported.",
+  "type": "string"
+}

addedInput schema / properties / estimatedHours
```
Added value: +{
+  "type": "number"
+}
```

addedInput schema / properties / image

Added value: +{
+  "description": "Header image URL.",
+  "type": "string"
+}

addedInput schema / properties / imageCarousel

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

addedInput schema / properties / keywords

Added value: +{
+  "description": "Comma-separated keyword string used by adventure-wide tag/search.",
+  "type": "string"
+}

addedInput schema / properties / level

Added value: +{
+  "additionalProperties": {},
+  "description": "Recommended character level range. Each side optional; null means unset.",
+  "properties": {
+    "max": {
+      "type": "number"
+    },
+    "min": {
+      "type": "number"
+    }
+  },
+  "type": "object"
+}

addedInput schema / properties / link

Added value: +{
+  "description": "URL-safe slug. Lowercase letters, numbers, and hyphens. Imagine auto-suggests at create time when omitted.",
+  "type": "string"
+}

addedInput schema / properties / name

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

addedInput schema / properties / partySize

Added value: +{
+  "additionalProperties": {},
+  "description": "Recommended party size range.",
+  "properties": {
+    "max": {
+      "type": "number"
+    },
+    "min": {
+      "type": "number"
+    }
+  },
+  "type": "object"
+}

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

addedInput schema / properties / ruleset

Added value: +{
+  "description": "Ruleset code. Required at create time; imagine has no default ruleset for adventures.",
+  "minLength": 1,
+  "type": "string"
+}

addedInput schema / properties / status

Added value: +{
+  "enum": [
+    "draft",
+    "playtest",
+    "published"
+  ],
+  "type": "string"
+}

addedInput schema / properties / summary

Added value: +{
+  "description": "Short summary; capped at 150 characters by imagine.",
+  "maxLength": 150,
+  "type": "string"
+}

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

addedInput schema / properties / world

Added value: +{
+  "description": "Optional World _id this adventure belongs to.",
+  "minLength": 1,
+  "type": "string"
+}

addedInput schema / required

Added value: +[
+  "name",
+  "ruleset"
+]

First observedSep 21, 2026

TDQS

A3.8/5.0

Behavior3/5

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

Annotations already convey that this is a mutating, non-destructive, non-idempotent operation, so the description does not need to repeat those. It adds useful ownership context and the no-default-ruleset caveat, but it does not disclose side effects, failure modes, or any creation-time behavior beyond that.

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, no wasted words, and the most important information is front-loaded. The ownership, required fields, and ruleset caveat are all stated efficiently.

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?

For a 20-parameter create tool with nested objects, the description establishes ownership and required fields but leaves optional behavior, defaults, status semantics, and nested-object handling to the schema. The output schema and annotations help, but the description alone is only minimally complete.

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?

The description adds essentially no parameter meaning beyond the schema: name and ruleset being required is already in the schema, and 'Other fields pass through to imagine' is vague. With 20 parameters and moderate schema coverage, the description does little to help an agent understand optional-field behavior or nested structures.

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 first sentence states a specific verb ('Create'), a unique resource ('adventure'), and scoping ('owned by the calling user'), making it easy to distinguish from sibling tools like imagine_create_world and imagine_create_adventure_page. The required-field note reinforces the core action without blurring the purpose.

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 establishes the context: use this when creating a new adventure for the calling user, and it calls out the ruleset requirement and the lack of a default. It does not explicitly name alternatives for when not to use this tool, so it falls just short of a 5.

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?