Embers: Tabletop RPG Toolkit

Get a vault character

vault_get_character

Read-onlyIdempotent

Fetch one character document by id. Defaults to a summary shape: combat-relevant top-level fields (attributes, defense, offense, AC, HP, actions, skills) preserved; bulk text bodies on populated rule/item/spell refs and inline snapshots trimmed; notes/trackables reduced to names + key fields. Pass detail: 'full' for the populated shape with every description inline. The companions[] array (buddy ties — see vault_attach_companion) rides along untrimmed in both shapes, overlay state included; each row's _ref is a bare character id you can fetch with this tool. linkGroup, when present, is the id shared by this persona's linked sheets in other rulesets (created via vault_spawn_linked_character); it rides reads only and is not writable through the update tool.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`id`	Yes	Mongo `_id` of the vault document.
`detail`	No	Response shape. 'summary' (default) trims the bulk text bodies on the populated rules / items / spells refs and on the inline snapshots, preserving combat-relevant top-level fields. 'full' returns the populated document with every description inline.	summary

Output Schema

TableJSON Schema

Name	Required	Description	Default
`_id`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedSep 21, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Annotations already establish readOnly/not destructive/idempotent, and the description adds substantial behavioral detail: what the summary shape trims, what `full` restores, that `companions[]` rides along untrimmed with `state`, and that `linkGroup` is read-only. 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.

Conciseness5/5

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

The description is dense but every sentence earns its place: the core action is front-loaded, followed by shape behavior, then related fields and cross-tool references. No filler or redundancy.

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 an output schema exists and annotations cover the read-only safety profile, the description is complete for an agent to call this tool correctly: it explains the id-based fetch, both response shapes, companion array handling, and linkGroup read semantics. Nothing important is left missing.

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 adds meaningful operational meaning beyond the schema, especially for `detail`: it explains exactly what gets preserved, trimmed, or inlined in each shape. It doesn't add anything new about `id`, but the schema already covers that fully.

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?

Opens with a specific verb+resource: 'Fetch one character document by id.' The scope is unambiguous and the name vault_get_character matches the action, while the description clearly differentiates it from list/search tools and other vault_get_* tools.

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?

The description gives clear context for choosing the summary vs. full detail shape, explains how companion `_ref` values can be resolved by this tool, and warns that `linkGroup` is read-only via the update tool. It does not explicitly name when to prefer this over vault_search_characters, but the usage is otherwise clear.

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?