Skip to main content
Glama

Embers: Tabletop RPG Toolkit

Add a character to a campaign

play_add_campaign_character

Attach a vault character to a play campaign so the character participates in play. Play places the attachment on the campaign leg matching the vault character's own ruleset — the campaign must have an active leg for that ruleset. Caller must hold a seat at the table (the campaign's owner, or an accepted gamemaster or player) and be able to edit the character (its owner, or an admin with Admin Mode on). A character can be on at most 10 active campaigns (400 for one more). The character also joins every World the campaign is linked to; the answer carries worldsNotJoined ([{ _id, name }], the linked Worlds a character already in as many Worlds as it may be did not join) and warning (a sentence saying so, or null; relay it to the user). Joining a World changes the character itself: the answer's updatedAt is its new version (null when it joined none), the baseUpdatedAt a later vault_update_character needs, and addedSkills lists the skill rows the join added. Use vault_search_characters to locate the character id first.

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": {
      "campaignId": "<campaignId>",
      "characterId": "<characterId>"
    },
    "name": "play_add_campaign_character"
  }
}

Input Schema

NameRequiredDescriptionDefault
npcNotrue if this character is added as a DM-controlled NPC; false / omitted = player character.
campaignIdYesCampaign id.
characterIdYesVault character id to add. Required.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior5/5

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

Beyond the annotations it discloses real consequences: the character joins every linked World and is itself modified, with updatedAt/baseUpdatedAt to carry into vault_update_character and addedSkills enumerating new skill rows. It also surfaces hard limits (10 active campaigns, 400 error) and the worldsNotJoined/warning response fields, which is well beyond what readOnlyHint/destructiveHint convey.

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?

The purpose is front-loaded, but the middle section is a dense run-on and the worldsNotJoined parenthetical ('the linked Worlds a character already in as many Worlds as it may be did not join') is close to unparseable. Several return-value details are explained at length despite an output schema existing.

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?

For a mutation with side effects on the character and on Worlds, the description covers auth prerequisites, limits, error behavior, and cross-tool consequences for vault_update_character, which is nearly everything an agent needs. The remaining gap is the NPC versus player-character distinction, which is left entirely to the schema.

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 each parameter is documented in the schema, so the schema does the heavy lifting. The description adds the sourcing of characterId (use vault_search_characters) but says nothing about the `npc` flag, whose behavioral implications for play are not obvious.

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 specific verb and resource ('Attach a vault character to a play campaign') and states the effect ('so the character participates in play'), which clearly separates it from siblings like play_add_campaign_item or play_add_campaign_rule that add other entity types to a campaign.

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?

It gives concrete preconditions — the campaign must have an active leg for the character's ruleset, the caller must hold a seat (owner, accepted GM or player), and must be able to edit the character — plus a pointer to vault_search_characters to find the id. It does not contrast with any alternative way to attach a character, 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