Embers: Tabletop RPG Toolkit

Add an item to a campaign's allowlist

play_add_campaign_item

Add a vault item to a campaign's allowlist. The item always lands on the leg matching the ITEM's own ruleset — the campaign must have a leg for that ruleset or play answers 400. The optional ruleset param never retargets; it only confirms the expected leg, and a mismatch answers 400. Caller must have 'contribute' on the campaign.

Input Schema

TableJSON Schema

Name	Required	Description
`itemId`	Yes	Vault document id (`itemId`). Required.
`ruleset`	No	Optional confirmation of the target leg's ruleset. The entity always lands on the leg matching its OWN ruleset — this param never retargets; when present, play verifies it matches that leg and answers 400 on a mismatch. Omit unless you want the placement double-checked.
`campaignId`	Yes	Campaign id.

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedSep 27, 2026

removedInput schema / properties / ruleset / enum

Removed value: -[
-  "5th Edition",
-  "5e24",
-  "PFRPG",
-  "PFRPG2",
-  "PF Playtest",
-  "Savage Worlds",
-  "Savage Embers",
-  "Solarian Conflict",
-  "Embers RPG",
-  "Universal",
-  "Fate Core",
-  "Fate Accelerated"
-]

addedInput schema / properties / ruleset / minLength
```
Added value: +1
```

First observedSep 21, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Goes well beyond the annotations (readOnly=false, destructive=false, idempotent=false) by disclosing two distinct 400 failure modes, the placement rule that the item lands on the leg matching its own ruleset, and the required 'contribute' permission. These are exactly the traits an agent cannot infer from the flags or schema.

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, front-loaded with the action, then the leg rule, then the permission. No filler, no restating of the title, and the 400 conditions are attached to the behaviour that causes them.

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?

With an output schema present, return values need no explanation. Preconditions, permission requirement and the two error paths are all covered, which is everything needed to invoke this mutation correctly.

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; the description still earns a bump by hammering the counter-intuitive point that `ruleset` never retargets and only acts as a confirmation that errors on mismatch. It clarifies intent rather than adding new syntax.

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?

Specific verb + resource ('Add a vault item to a campaign's allowlist') that cleanly separates it from the many play_add_campaign_* siblings (spell, rule, character, leg). An agent knows exactly what is being added and to what container.

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 the operative preconditions: the campaign must already have a leg for the item's ruleset, and the caller must hold 'contribute'. It does not, however, name when to prefer this over sibling allowlist tools or what to do instead when the leg is missing (e.g. call play_add_campaign_leg).

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?