Embers: Tabletop RPG Toolkit

Search vault rules

vault_search_rules

Read-onlyIdempotent

Search the rules library the user has access to (stock content plus their own house rules). Use this to locate a rule by name, type (the type field lists the rule types), or ruleset. Defaults to a compact summary shape (identification + summary + categories + publisher / source); pass detail: 'full' to receive each rule's full description and embedded sub-document arrays inline.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`name`	No	Substring match on rule name (case-insensitive). Use `^name$` for an exact match.
`skip`	No	Pagination offset; pair with `limit` to walk results.
`sort`	No	Comma-separated field list. Prefix with `-` for descending (e.g. `-updatedAt,name`).
`type`	No	Rule category to filter to.
`limit`	No	Page size; defaults to 50 when omitted. Hard cap of 200.
`stock`	No	true = official/WOTC content only; false = user-authored house rules only; omit to include both.
`detail`	No	Response shape. 'summary' (default) returns identification + summary fields; 'full' returns the complete document shape (every field inline) that non-MCP clients receive by default.	summary
`ruleset`	No	Ruleset code, from list_rulesets.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`results`	No
`pagination`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedSep 27, 2026

changedInput schema / properties / ruleset / description

Previous value: -"Ruleset code (e.g. '5th Edition', '5e24', 'PFRPG', 'Savage Worlds', 'Universal')."New value: +"Ruleset code, from list_rulesets."

changedInput schema / properties / type / enum

Previous value: -[
-  "Ability",
-  "Feat",
-  "Action Card",
-  "Hindrance",
-  "Edge",
-  "Class",
-  "Background",
-  "Race",
-  "Species",
-  "Ancestry",
-  "Glossary",
-  "Stunt",
-  "Extra"
-]New value: +[
+  "Ability",
+  "Feat",
+  "Glossary",
+  "Action Card",
+  "Hindrance",
+  "Edge",
+  "Class",
+  "Background",
+  "Race",
+  "Species",
+  "Ancestry",
+  "Stunt",
+  "Extra"
+]

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 already declare readOnly/idempotent/non-destructive, so the safety profile is covered. The description adds real behavioral value by disclosing the default response shape and the opt-in `detail: 'full'` payload expansion, which changes what the caller receives.

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, front-loaded with scope and purpose, then the filter axes, then the response-shape default. No filler or repetition.

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?

With 8 optional params, an output schema, and complete annotations, the description covers the decision-relevant knobs (filters and detail mode). Pagination/sort/stock are left to the schema, which is acceptable but a brief note on paging would make it fully self-sufficient.

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 goes further by explaining what each `detail` mode actually returns (identification/summary/categories/publisher vs full description plus embedded sub-document arrays) and by framing the filterable fields, adding meaning beyond the schema's own wording.

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+resource ('Search the rules library') plus the access scope (stock content plus user house rules), and names the three lookup axes (name, type, ruleset). An agent can distinguish it from vault_get_rule and list_rulesets without opening either schema.

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?

'Use this to locate a rule by name, type, or ruleset' gives clear positive usage context, and the mention of ruleset codes implies list_rulesets as a feeder. It stops short of explicit exclusions (e.g., 'use vault_get_rule when you already have an id').

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?