Embers: Tabletop RPG Toolkit

Get a play campaign

play_get_campaign

Read-onlyIdempotent

Fetch one campaign by id, including settings and any DM/player metadata. Calling user must be a member (DM or player). The campaign's ruleset-specific material lives in its legs array — one entry per ruleset, each carrying { ruleset, active, rules, items, spells, characters }; inactive legs are hidden from normal UI but never deleted. There is no campaign-level ruleset field. Defaults to a summary shape: each leg's raw rule/item/spell ObjectId arrays are replaced with resolved [{ _id, name }, ...] lists the LLM can act on. Pass detail: 'full' to receive the raw ObjectId arrays instead. The response's imagineAdventures array ([{ id, name }, ...]) lists the Imagine adventures linked to this campaign — read-only here (maintained from the Imagine side); its ids are the valid values for a session's imagineAdventureId tag.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`id`	Yes	Mongo `_id` of the campaign.
`detail`	No	Response shape. 'summary' (default) trims raw-ObjectId arrays and full character sheets to a compact LLM-friendly form; 'full' returns the populated document with every field inline.	summary

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedSep 21, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Beyond the readOnlyHint/idempotentHint annotations, it discloses important non-obvious behavior: inactive legs are hidden but never deleted, there is no campaign-level ruleset field, summary replaces ObjectId arrays with resolved lists, and imagineAdventures is maintained externally and read-only. This materially improves safe and correct use.

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 dense but well ordered: main operation, prerequisite, data layout, detail behavior, and cross-resource linkage. It is longer than strictly necessary (some detail parallels the schema), but every sentence conveys useful context.

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?

For a read-only fetch with an output schema and annotations, the description covers the essential invocation knowledge: membership requirement, response shape control, legs semantics, and imagineAdventures linkage. Nothing an agent needs to call or interpret this tool is missing.

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 100%, so the baseline is 3, but the description adds genuine meaning: it explains what summary vs full means for the legs arrays and explicitly notes that imagineAdventure ids are valid values for a session tag. The id parameter is already fully described by 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 a specific action and target: fetch one campaign by id, and it lists what is included (settings and DM/player metadata). This clearly separates it from list-style siblings like play_list_my_campaigns and from other play_get_* resources.

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?

It states the prerequisite that the caller must be a member and gives concrete guidance on choosing detail=summary vs full. It does not explicitly name alternatives or when not to use this tool, but the intended invocation context 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?