Skip to main content
Glama

Embers: Tabletop RPG Toolkit

List a character's Worlds

vault_list_character_worlds
Read-onlyIdempotent

List the imagine Worlds a character is in, in the order it joined them: [{ _id, name, link }] (link is null for a World with no link name). A character can be in many Worlds; while its owner can view a World, the character is offered what the World adds, not offered the stock the World hides, gets its extra skills, and is offered its extra damage types of its ruleset. Every World the character is in is listed, including one its owner can no longer view. Add or remove a World with imagine_add_character_to_world / imagine_remove_character_from_world. Readable by whoever may view the character's sheet; 404 for an unknown character or one the user may not view.

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

Input Schema

NameRequiredDescriptionDefault
idYesMongo `_id` of the character.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior5/5

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

Beyond the annotations (readOnly, idempotent, non-destructive), it discloses the ordering guarantee, that Worlds whose owner lost visibility are still returned, the 404 behavior for unknown or forbidden characters, and the effective gameplay consequences of membership. That is real behavioral context the agent cannot get from structured fields.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loads the verb and return shape well, but the middle sentence is a run-on that mixes visibility rules with ruleset mechanics ('offered what the World adds, not offered the stock the World hides, gets its extra skills...'), which is hard to parse and partly redundant with the output schema.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Access rules, error behavior, ordering, and alternatives are all covered, and an output schema exists so return details are already structured. The only miss is that the inline return shape partially duplicates the output schema, and pagination/size expectations are unaddressed.

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 the single `id` parameter is already documented as the Mongo `_id` of the character. The description adds nothing about the identifier's format or sourcing, so the baseline 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 with scope: 'List the imagine Worlds a character is in, in the order it joined them', and pins the return shape `[{ _id, name, link }]`. It is clearly distinct from the add/remove siblings it names and from the world-oriented listing siblings.

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 routes mutation intent elsewhere: 'Add or remove a World with imagine_add_character_to_world / imagine_remove_character_from_world'. It also gives access context ('Readable by whoever may view the character's sheet'), though it never states a when-not-to-use condition or a competing read tool.

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