Skip to main content
Glama

Embers: Tabletop RPG Toolkit

Spawn a linked character sheet in another ruleset

vault_spawn_linked_character

Create a linked sibling sheet for a character the user may edit (their own, or any for an admin with Admin Mode on), in a different ruleset; the new sheet belongs to the source's owner — the same persona with sheets in multiple rulesets, tied together by a shared linkGroup id. The server builds the new sheet from the target ruleset's template and copies only the descriptive/identity fields in the sync manifest (name, description, image, appearance, personality, and similar); mechanical and build data (class, level, attributes, skills, rules/items/spells, notes) stays ruleset-local and starts fresh. After the spawn, edits to a manifest field on any linked sheet cascade to its siblings automatically. Play campaign assignments of the source are replicated onto campaign legs matching the new ruleset where they exist. One sheet per ruleset per group: vault answers 409 when the source is already that ruleset or a linked sibling already occupies it, 403 when the source's owner lacks the grant for a restricted ruleset, and 404 for an unknown source or one the user may not edit. This is NOT vault_clone_character — clone deep-copies the whole ruleset-specific sheet; spawn deliberately does not. Before spawning, check vault_list_convertible_characters for the target ruleset: when it lists this character, vault converts it into that ruleset (vault_preview_character_conversion, then vault_convert_character), carrying its classes, features, spells, and items over, so offer the conversion and spawn a blank sheet only when the user wants one. When the list does not name this character for that ruleset (it answers { ruleset: null, characters: [] }, or leaves the character out), spawn as described above.

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_spawn_linked_character"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesMongo `_id` of the source character (owned by the calling user, or any character for an admin with Admin Mode on). The new sheet belongs to the source's owner, so the ruleset grant and the character limit are the owner's.
rulesetNoRuleset code for the new linked sheet, from list_rulesets (the codes this account can use). Required. Must differ from the source's ruleset; restricted rulesets require the owner's entitlement grant (vault answers 403).

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / id / description
      Previous value: -"Mongo `_id` of the source character (owned by the calling user)."New value: +"Mongo `_id` of the source character (owned by the calling user, or any character for an admin with Admin Mode on). The new sheet belongs to the source's owner, so the ruleset grant and the character limit are the owner's."
    • changedInput schema / properties / ruleset / description
      Previous value: -"Ruleset code for the new linked sheet, from list_rulesets (the codes this account can use). Required. Must differ from the source's ruleset; restricted rulesets require an entitlement grant (vault answers 403)."New value: +"Ruleset code for the new linked sheet, from list_rulesets (the codes this account can use). Required. Must differ from the source's ruleset; restricted rulesets require the owner's entitlement grant (vault answers 403)."
  2. Changed1 schema field changed
    • changedInput schema / properties / ruleset / description
      Previous value: -"Ruleset code for the new linked sheet (e.g. '5th Edition', '5e24', 'Fate Core'). Required. Must differ from the source's ruleset; restricted rulesets require an entitlement grant (vault answers 403). Check list_rulesets for the codes this account can use."New value: +"Ruleset code for the new linked sheet, from list_rulesets (the codes this account can use). Required. Must differ from the source's ruleset; restricted rulesets require an entitlement grant (vault answers 403)."
  3. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations only declare the basic mutation profile (readOnlyHint=false, destructiveHint=false, idempotentHint=false, openWorldHint=false); the description adds substantially more: exactly which fields copy versus start fresh, the post-spawn cascade on manifest fields, campaign-assignment replication, the one-sheet-per-ruleset constraint, and the 409/403/404 conditions with their causes. The only thing left implicit is that failure leaves the source untouched, which is minor.

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?

It is front-loaded with the core action and the copy/not-copy split before moving to side effects, errors, and alternatives. The prose is dense and the final sentence about the empty-list case is convoluted, but almost every sentence carries decision-relevant information rather than filler.

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 non-idempotent mutation with an output schema and annotations, the description covers the prerequisites, the field-copy semantics, cascading edits, campaign side effects, and the full error taxonomy. An agent has everything needed to decide whether to call it and what to expect.

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 already 100%, so the schema carries most of the burden. The description still adds constraint-level meaning beyond the field docs: the owner (not the caller) bears the ruleset grant and character limit, and the new sheet must occupy a different ruleset, with the 403 path tied to restricted rulesets.

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?

The first sentence names a specific verb (create a linked sibling sheet), the resource (character sheet), and the scope (different ruleset, same owner). It explicitly contrasts with vault_clone_character ('clone deep-copies the whole ruleset-specific sheet; spawn deliberately does not') and with the conversion path, so an agent can separate this from every neighboring tool without opening a schema.

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?

It gives a concrete precondition workflow (call vault_list_convertible_characters first, then vault_preview_character_conversion / vault_convert_character when the character is listed) and states when to fall back to spawn (only when the user wants a blank sheet or the character is absent from the list). It also names the when-not case for clone, which is unusually explicit.

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