Skip to main content
Glama

Embers: Tabletop RPG Toolkit

Add a Character to a World

imagine_add_character_to_world
Idempotent

Add a vault Character (any type, monsters included) to a World. A Character can be in at most 10 Worlds at once (400 for one more). While the Character's owner can view the World, the Character is offered what the World adds as house rules, is not offered the stock content the World hides (unless another of its Worlds keeps it), gets the World's extra skills of its ruleset as skill rows it does not already have, written now, and is offered the World's extra damage types of its ruleset. The caller must be able to edit the Character and view the World (403 otherwise). Adding a Character already in the World changes nothing. Returns { characterId, worlds: [{ _id, name, link }], updatedAt, addedSkills }: every World the Character is now in, in the order it joined them, the Character's new updatedAt (adopt it for a following vault_update_character; null when the Character was already in the World and nothing changed), and the skill rows the add stored on it.

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>",
      "characterId": "<characterId>"
    },
    "name": "imagine_add_character_to_world"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesMongo `_id` of the World.
characterIdYesMongo `_id` of the vault Character. Find it with vault_search_characters, vault_search_monsters, or play_list_my_characters.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior5/5

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

Annotations only declare the generic non-read-only, idempotent, open-world profile; the description goes far beyond that with the world-membership cap (10, 400 for one more), authorization failure mode (403), the propagation side effects (house rules offered, hidden stock suppressed unless another World keeps it, extra skills written now, extra damage types offered), and the exact idempotency semantics. This is precisely the side-effect disclosure a mutating tool needs, and it is consistent with idempotentHint=true and destructiveHint=false.

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 purpose is front-loaded in sentence one and every later clause carries a distinct behavioral fact. The middle sentence is an overly long run-on that bundles five separate effects (view access, house rules, hidden stock, skill rows, damage types) and is harder to parse than it needs to be.

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?

Despite a rich output schema, the description still explains the return payload's non-obvious parts — the meaningful null `updatedAt` when nothing changed and the `addedSkills` rows — plus the ordering of `worlds`. For a tool with real side effects on a shared Character, nothing an agent needs before calling it is missing.

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 coverage is 100% and both parameters already document that they are Mongo `_id` values, including which sibling tools find a characterId. The description adds no syntax, format, or edge-case meaning for `id` or `characterId`, so it rests at the baseline where the schema carries the load.

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 and both resources: 'Add a vault Character (any type, monsters included) to a World.' The parenthetical ('monsters included') pre-empts a likely agent assumption and distinguishes it from sibling tools like imagine_remove_character_from_world or imagine_add_world_skill.

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 sets clear preconditions ('The caller must be able to edit the Character and view the World') and a when-not condition ('Adding a Character already in the World changes nothing'), and the schema points to discovery siblings for characterId. It stops short of naming an explicit alternative tool and its selecting condition, so it is not a full 5.

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