Embers: Tabletop RPG Toolkit

Clone a vault character

vault_clone_character

Duplicate any vault character the calling user can see — their own characters, stock template content, and other users' authored characters are all valid sources. The server does the deep-copy (stats, skills, items, rules, spells, trackables, all of it) — caller passes only the source id and optionally a new name. The new character is owned by the caller (not the source's original owner) and counts against the caller's character entitlement limit. When name is omitted, the clone is named <source name> (Copy). Use this instead of fetching the source sheet and re-POSTing it via vault_create_character.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`id`	Yes	Mongo `_id` of the source character to clone.
`name`	No	Optional name for the new character. Defaults to `<source name> (Copy)` when omitted, matching the web client's clone behavior. Whitespace-only values are rejected at the schema layer so a silently-trimmed-to-empty name can't reach the backend.

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

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?

Adds substantial behavior beyond annotations: deep-copy semantics, ownership transfer to the caller, entitlement/quota impact, and default naming when name is omitted. These are non-obvious consequences not inferable from readOnlyHint or destructiveHint.

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?

Four tight, purposeful sentences. It front-loads the core scope, then covers mechanics, ownership/quota, and the alternative without 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?

For a two-parameter tool with an output schema, this is complete: it covers source scope, deep-copy behavior, ownership, quota effects, naming, and the correct alternative. Nothing essential is missing for an agent to invoke it correctly.

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

Parameters3/5

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

Schema description coverage is 100%, and the schema already documents both parameters, including the default naming behavior and whitespace validation. The description reiterates that name is optional but adds no genuinely new parameter semantics.

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 ('Duplicate any vault character') and enumerates valid source types, which clearly distinguishes it from vault_create_character and other vault tools. It also names the key alternative explicitly.

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?

Directly tells the agent when to use this tool: whenever cloning any visible character. It names the alternative (vault_create_character) and explains why this tool should be preferred over fetching and re-POSTing.

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?