Skip to main content
Glama

Embers: Tabletop RPG Toolkit

List the user's characters that can be converted into a ruleset

vault_list_convertible_characters
Read-onlyIdempotent

List the calling user's own characters that vault offers a conversion for into the given ruleset (pass a ruleset code from list_rulesets). Use it when the user wants a version of an existing character in a newer ruleset and has not said which character, or to find out whether any conversion is on offer. Vault decides everything here: which rulesets convert into the one asked for, and which characters are offered (the user's own player characters, not monsters, that have no linked sheet in that ruleset yet, or one that is still blank). Returns { ruleset: { from, to }, characters: [{ _id, name, image, ruleset, core, updatedAt, fills }] }, by name: ruleset carries the two ruleset codes, and fills is true when converting that character fills in a blank linked sheet it already has, so it takes no character slot. A ruleset nothing converts into, or one the user is not entitled to, answers { ruleset: null, characters: [] }: say that no conversion is offered. Then call vault_preview_character_conversion with the chosen character's _id. Only the caller's own characters are ever listed; for another user's character an admin goes straight to the preview.

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": {
      "ruleset": "<ruleset>"
    },
    "name": "vault_list_convertible_characters"
  }
}

Input Schema

NameRequiredDescriptionDefault
rulesetYesCode of the ruleset the user wants a converted character in (a code from list_rulesets).

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so safety is covered; the description adds substantial behavior beyond that — vault itself decides which rulesets convert and which characters are offered, and the eligibility rules are spelled out. It also discloses the empty-result case (ruleset null, empty characters array) and instructs the agent to report that no conversion is offered, plus explains the `fills` flag and its character-slot implication.

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 paragraph is front-loaded with purpose, then conditions, then result semantics and the next call, so an agent can stop reading early. It is dense but nearly every clause carries information; the restated return shape overlaps with the existing output schema, which is the main avoidable bulk.

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 single-parameter listing tool with an output schema, the definition covers purpose, eligibility, empty-result handling, field semantics for `fills`, and the required follow-up call. Nothing an agent needs to select or invoke it correctly is missing.

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

Parameters4/5

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

Schema coverage is 100% and the single parameter is already documented as a ruleset code, so the baseline is 3. The description adds modest but real meaning: the code must come from list_rulesets, and the conversion direction (which rulesets convert into the requested one) is decided by vault, not specified by the caller; it also notes that an unentitled ruleset yields a null result rather than an error.

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 description opens with a precise verb and resource: list the calling user's own characters for which vault offers a conversion into a given ruleset. It distinguishes this from nearby listing tools by naming the exact eligibility filters (own player characters, not monsters, no linked sheet in that ruleset or a blank one).

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?

It states explicit triggers (the user wants an existing character in a newer ruleset and hasn't said which one, or wants to know whether any conversion exists) and names the follow-up tool, vault_preview_character_conversion, with the identifier to pass. It also carves out an exclusion: for another user's character an admin goes straight to the preview, skipping this 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