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 be the campaign's owner, a gamemaster or player with an accepted seat (watchers excluded), or an admin with Admin Mode on.

Input 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

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

Behavior4/5

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

Annotations indicate non-readonly, open-world, non-idempotent, non-destructive. Description adds critical behavior: ruleset-based placement, 400 on missing leg or ruleset mismatch, and authorization requirements (owner, gamemaster, player with accepted seat, admin with Admin Mode). This goes well beyond annotations.

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 core action and placement, then permissions. No wasted words.

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?

Covers placement rules, error conditions, and authorization. Output schema exists, so return values needn't be explained. Missing explicit mention of idempotency or side effects beyond allowlist addition, but adequate.

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 baseline is 3. Description clarifies that the `ruleset` param never retargets and only confirms the expected leg, adding meaning beyond the schema's description, which already says similar but the tool description reinforces the 'never retargets' point.

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?

States a specific verb ('Add') and resource ('vault item to a campaign's allowlist'), clearly distinguishing from siblings like play_add_campaign_character or play_add_campaign_spell.

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?

Explains that the item lands on the leg matching its own ruleset and that the campaign must have a leg for that ruleset, else 400. Implicitly gives when-to-use and constraints, but doesn't explicitly name alternatives or exclusions.

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?