Skip to main content
Glama

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 reduced to names; trackables reduced to name, counts, type, and the fields that link and refill them (_rule, _spell, _item, slotLevel, recovery), so the list can be sent back whole. 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.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "id": "<id>"
    },
    "name": "vault_get_character"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesMongo `_id` of the vault document.
detailNoResponse 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

NameRequiredDescriptionDefault
_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already declare read-only, idempotent, non-destructive, closed-world, but the description goes well beyond them: it enumerates exactly which fields survive trimming, how notes and trackables are reduced, and that companions ride untrimmed in both shapes with overlay `state`. It also discloses that `linkGroup` is read-only and cannot be written through the update tool, which an agent could not infer from the schema or 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 core action is front-loaded in the first sentence and every subsequent clause carries factual content rather than filler. It is dense to the point of being run-on, stacking parentheticals and field lists in single sentences where enumerations would scan faster, but little is genuinely wasted.

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?

For a two-parameter read-by-id tool with an output schema, the description supplies everything needed: default behavior, the opt-in full mode, what trimming affects, and the read-only status of `linkGroup`. Nothing required to call it correctly or interpret the summary shape is 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 schema already documents both parameters and the summary/full enum, making 3 the baseline. The description adds meaning the schema does not: companions are untrimmed in either mode, trackables retain `_rule`, `_spell`, `_item`, `slotLevel`, `recovery`, and `_ref` values are themselves fetchable ids, which shapes how an agent should reuse the result.

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 and resource ('Fetch one character document by id') and immediately qualifies the shape returned. The repeated emphasis on character-specific structures (attributes, defense, HP, actions, skills, companions) distinguishes it from sibling getters like vault_get_item and vault_get_rule.

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?

Explicitly tells the agent to use the default summary shape for list-round-trips and to pass `detail: 'full'` when every description must be inline, which is actionable when-to-use guidance. It also notes that companions' `_ref` values are bare character ids fetchable with this same tool. It stops short of contrasting with play-side character readers, so no exclusions are stated.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources