Skip to main content
Glama

Embers: Tabletop RPG Toolkit

Remove a Character from a World

imagine_remove_character_from_world
Idempotent

Take a vault Character out of a World. Nothing else on the sheet changes: skills, rules, spells, and items the Character got while in the World stay. Allowed for whoever may edit the Character, edit the World, or is a contributor of the World (403 otherwise). Removing a Character that is not in the World answers 404 and changes nothing. Returns { characterId, worlds: [{ _id, name, link }], updatedAt }: the Worlds the Character is still in and its updatedAt (adopt it for a following vault_update_character).

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_remove_character_from_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.5/5.0
Behavior5/5

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

Goes well beyond the annotations by disclosing exactly what is preserved (skills, rules, spells, items gained in the World), the authorization failure mode (403), the not-found behavior (404 with no changes), and the return payload. This is consistent with destructiveHint=false and idempotentHint=true, since the operation only unlinks and a repeat call is a no-op.

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?

Front-loads the action, then the invariant, then permissions, then error cases, then the return shape. Every sentence carries distinct information with no 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 two-parameter unlink operation with annotations and an output schema, the description covers action, side effects, authorization, error semantics, and the follow-up use of updatedAt. Nothing an agent needs to invoke it correctly 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 are documented in the schema, including how to find characterId. The description adds no syntax or format detail for id or characterId beyond what the schema already provides, so the baseline of 3 applies.

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: 'Take a vault Character out of a World.' It immediately clarifies the scope of the change ('Nothing else on the sheet changes'), which distinguishes it from a delete-character operation and from the add counterpart.

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?

Gives clear context for when the call is valid: permission model (edit Character, edit World, or World contributor, else 403) and the no-op case (404 if the Character is not in the World). It also points to a follow-up tool (vault_update_character) for the returned updatedAt. It does not explicitly name an alternative tool or exclusion, so it stops short of a 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