Skip to main content
Glama

Embers: Tabletop RPG Toolkit

Get a campaign's party order

play_get_campaign_party_order
Read-onlyIdempotent

Read a campaign's Party Order: its marching order and its watches. partyOrder.ranks runs front to back (rank 1 is the front); each rank's characters run left to right. partyOrder.watches lists the watches in order, each with the characters assigned to it; a character may stand more than one watch. Characters are vault character ids, the _id of the rows play_list_campaign_characters returns (use it for names). A campaign that has never set one answers one empty rank and three empty watches. Readable by the campaign's GM and accepted players; watchers and pending invitees get 403.

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>"
    },
    "name": "play_get_campaign_party_order"
  }
}

Input Schema

NameRequiredDescriptionDefault
campaignIdYesMongo `_id` of the campaign.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.5/5.0
Behavior5/5

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

Goes well beyond the readOnly/idempotent annotations by disclosing the authorization model (403 for watchers and pending invitees) and the default return shape for a campaign that has never configured a party order. It also clarifies that a character may appear on multiple watches, which is behavioral detail an agent cannot infer 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.

Conciseness5/5

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

Front-loads the purpose, then layers return-shape semantics, id provenance, empty-state behavior, and permissions in a tight sequence. Every sentence contributes information not available in the schema or annotations; there is no filler.

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 single-parameter read tool with a full output schema, this covers everything an agent needs: what it returns, how to interpret rank and watch ordering, how to resolve character ids, the empty-state default, and the permission boundary. Nothing material is missing.

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 sole parameter campaignId is documented as the Mongo `_id` of the campaign, so the schema already carries the semantics. The description adds nothing further about the parameter itself, making the baseline 3 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 — 'Read a campaign's Party Order' — and immediately scopes it to marching order plus watches, which no other sibling covers. An agent can distinguish it from play_update_campaign_party_order and play_list_campaign_characters on name and description alone.

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 situational context: readable by the campaign's GM and accepted players, with watchers and pending invitees receiving 403, and points to play_list_campaign_characters when names are needed. It stops short of naming the write counterpart (play_update_campaign_party_order) as the alternative for changes, so it is strong but not fully explicit about when-not-to-use.

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