Embers: Tabletop RPG Toolkit

Get a vault authoring guide

vault_get_authoring_guide

Read-onlyIdempotent

Fetch a markdown reference guide that teaches the conventions for authoring a specific entity type in a specific ruleset. Returns the full markdown body, including front-matter metadata (ruleset, entityType, version) at the top. Published for 5e24: { entityType: 'monster' } — monster stat-block authoring (field map, AC base calc, CR-to-level-to-XP table, action types, spell formatting, resistances/immunities, keywords, high-PB adjustment, worked example), authored via vault_create_character + vault_update_character; { entityType: 'rule' } — classes / species / backgrounds / feats / abilities (the type taxonomy, the parent→Ability grant model, type-specific section fields, and the shared mechanics blocks: proficiencyChoices, spellChoices, spellListChoices, preparedSpells, freeCast, uses, ruleChoice, statBonuses), authored via vault_create_rule + vault_update_rule; { entityType: 'spell' } — the 5e24 Spell Detail header (casting time / range / area / components / duration), the categories (Class(es)) membership convention, and the damage/healing/effect mechanics blocks, authored via vault_create_spell + vault_update_spell. Call this BEFORE authoring the matching entity so the result follows the established conventions instead of inferring shape from one-off samples. Returns a 'not found' tool error when the requested entityType / rulesetCode combination does not have a published guide yet.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`entityType`	Yes	Entity the guide covers. Published for 5e24: 'monster', 'rule' (classes / species / backgrounds / feats / abilities), and 'spell'. Other entity types and rulesets land as separate guides over time. Lowercase.
`rulesetCode`	No	Ruleset data value (e.g. '5th Edition', '5e24', 'PFRPG', 'PFRPG2', 'PF Playtest', 'Savage Worlds', 'Savage Embers', 'Solarian Conflict', 'Embers RPG'). Use the data value, not the display label.

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedSep 21, 2026

TDQS

A4.9/5.0

Behavior5/5

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

Beyond the readOnly/idempotent annotations, the description discloses the returned markdown structure (front-matter metadata, full body), the error behavior for unpublished combinations, and the taxonomy of published guides. No contradiction with annotations.

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 long but information-dense, with the core purpose in the first sentence and then structured content per entity type. Could be split into bullets for readability, but every sentence carries substance.

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?

Given the 2-parameter schema and output schema, the description covers usage timing, return content, error cases, and per-type content. An agent can confidently invoke this tool for any supported entity type.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Even though schema covers all parameters, the description amplifies them: enumerates the valid entityType values with their authoring tools, and adds the crucial rule 'Use the data value, not the display label' for rulesetCode. This is exactly the kind of context agents need.

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 ('Fetch'), resource ('markdown reference guide'), and scope ('for authoring a specific entity type in a specific ruleset'). Clearly distinguishable from sibling authoring tools by its read-only guide role.

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

Usage Guidelines5/5

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

Explicitly instructs to call this BEFORE authoring the matching entity, and names the upstream authoring tools (vault_create_character, vault_create_rule, etc.) for each entity type. The 'not found' error condition also helps the agent decide when the guide is unavailable.

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?