Embers: Tabletop RPG Toolkit

List rules allowed in a campaign

play_list_campaign_rules

Read-onlyIdempotent

List the campaign's house rules: the rules it holds as active house-rule associations. Subset of the broader vault catalog. Each sits on the leg matching its own ruleset: omit ruleset to list the rules across every leg, or set it to scope the list to that one leg.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`ruleset`	No	Optional leg filter. Omitted, the list unions entries across every leg of the campaign; set to a ruleset to scope the list to that leg only.
`campaignId`	Yes	Mongo `_id` of the campaign.

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

A3.5/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds the semantic detail that results are 'active house-rule associations' scoped per leg, but nothing about volume, ordering, or permissions 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three compact sentences, front-loaded with the core purpose before the leg-scoping detail. Some phrasing ('the rules it holds as active house-rule associations') is mildly redundant but not wasteful.

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?

An output schema exists, so return values need not be explained, and both parameters are schema-documented. The description covers purpose and the key scoping behavior adequately for a simple two-parameter list tool.

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?

Schema description coverage is 100%, so both parameters are already fully documented in the schema, including the ruleset leg-filter semantics. The description largely restates that same behavior, adding no syntax or format detail beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('List the campaign's house rules') and clarifies that these are active house-rule associations, a subset of the broader vault catalog. This distinguishes it from catalog-wide siblings like vault_search_rules and list_rulesets, though it never names those tools directly.

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

Usage Guidelines3/5

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

The description gives usage context for the ruleset parameter (omit to union all legs, set to scope to one leg), which is genuinely helpful. However, it offers no when-to-use guidance relative to siblings such as play_add_campaign_rule or vault_search_rules.

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?