Skip to main content
Glama

Embers: Tabletop RPG Toolkit

List a World's Characters

imagine_list_world_characters
Read-onlyIdempotent

List the vault Characters in a World (any type, monsters included), by name unless sorted, one page at a time. Returns { results, pagination }: each result is { _id, name, image, type, ruleset, owner, group } (owner carries public display fields only; group is monster for a monster, npc for a Character flagged an NPC on its row in a campaign linked to the World, else pc), and pagination is { count, limit, skip }; walk further pages with skip. Only someone who manages the World (whoever may edit it, or a contributor of it) may list them: the app answers 403 to anyone else, and 404 for an unknown or deleted World. Add or remove a Character with imagine_add_character_to_world / imagine_remove_character_from_world; vault_list_character_worlds lists one Character's Worlds.

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": "imagine_list_world_characters"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesMongo `_id` of the World.
nameNoSubstring match on the Character's name (case-insensitive). Use `^name$` for an exact match.
skipNoPagination offset; pair with `limit` to walk results.
sortNoComma-separated field list. Prefix with `-` for descending (e.g. `-updatedAt,name`). By name when omitted.
limitNoPage size; defaults to 50 when omitted. Hard cap of 200.

Output Schema

NameRequiredDescriptionDefault
resultsNo
paginationNo

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 already declare readOnly/idempotent/non-destructive, and the description adds substantially beyond that: the permission model (World editors or contributors), concrete failure codes (403 for unauthorized, 404 for unknown/deleted World), pagination-by-skip behavior, and the derivation rule for `group` values. This is exactly the behavioral context annotations cannot carry.

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?

Front-loaded with the core action, then return shape, then access rules, then related tools — a sensible progression. The return-shape sentence is dense and long, and partly duplicates the available output schema, but nothing is wasted.

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 read-only, paginated list tool with an output schema, the description covers access control, error outcomes, pagination continuation, and sibling routing. An agent has everything needed to invoke it correctly and interpret failures.

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%, so limit cap, skip offset, sort syntax, and name matching are all documented in the schema. The description only restates the default ordering ('by name unless sorted') and the skip-walking pattern, adding little new meaning. Baseline 3 is appropriate.

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 ('List the vault Characters in a World'), scopes it ('any type, monsters included'), and implies the ordering rule. This is clearly distinguishable from siblings like vault_list_character_worlds, which the description names as the inverse lookup.

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 explicit routing to alternatives for mutation (imagine_add_character_to_world / imagine_remove_character_from_world) and for the reverse query (vault_list_character_worlds). It does not spell out a when-not-to-use case, but the guidance is clear enough for selection.

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