Skip to main content
Glama

Embers: Tabletop RPG Toolkit

Change a campaign player's role

play_set_campaign_player_role
DestructiveIdempotent

Change the role of a seat in a campaign, accepted or still a pending invite. Caller must be the campaign's GM (its owner or an accepted gamemaster). The campaign owner's role cannot be changed, and a caller cannot change their own. playerId is the player-record id returned by play_list_campaign_players (the embedded player doc id, NOT the user's id).

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>",
      "playerId": "<playerId>",
      "role": "<role>"
    },
    "name": "play_set_campaign_player_role"
  }
}

Input Schema

NameRequiredDescriptionDefault
roleYesThe seat's new role. 'watcher' is read-only; 'gamemaster' grants co-DM permissions.
playerIdYesEmbedded player document id from play_list_campaign_players.
campaignIdYesCampaign id.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=true, so safety profile is partly covered. The description adds authorization requirements and immutability constraints not present in the annotations, which is genuine behavioral value. What is missing is a statement of consequence — e.g. that demoting a gamemaster to watcher revokes their DM permissions — which matters for a destructive mutation.

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?

Three tight sentences, front-loaded with the operation, then authorization, then parameter sourcing. Every sentence carries information an agent needs; nothing is redundant.

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?

Output schema and annotations cover return values and safety profile, and the description fills the remaining gaps the agent needs: who may call it, what cannot be changed, and where playerId comes from. Nothing material is missing for correct invocation.

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%, so the baseline is 3. The description still adds disambiguation beyond the schema by stressing that playerId is the embedded player-record id returned by play_list_campaign_players and explicitly NOT the user's id — a common source of wrong calls. Role enum semantics live in the schema, so no further credit is warranted.

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 (change a seat's role in a campaign) and adds scope detail that separates it from siblings: it covers accepted seats and pending invites, distinguishing it from play_invite_campaign_player and play_remove_campaign_player. An agent can identify the operation without opening the schema.

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 preconditions for use: the caller must be the campaign GM (owner or accepted gamemaster). It also states two hard exclusions (owner's role cannot be changed, callers cannot change their own role), which effectively tells the agent when the call will fail. It does not explicitly name sibling alternatives such as remove vs invite, so it falls 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