Skip to main content
Glama

Embers: Tabletop RPG Toolkit

Create a play campaign

play_create_campaign

Create a new campaign owned by the calling user. Required: name. ruleset becomes the campaign's first leg (campaigns hold ruleset-specific material in per-ruleset legs; add more with play_add_campaign_leg). Play writes only name, summary, description, image, public, hideSections, dismissedSessionZeroNudge, xCardEnabled, showCreatureDetails, and autoRollInitiative at create and ignores any other field; seats come from the invite tools. Creating it public needs Premium, VIP, or admin.

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

Input Schema

NameRequiredDescriptionDefault
nameYesCampaign name. Required.
imageNoImage URL. Stored as a plain string.
publicNoWhether non-members can see the campaign. Making the campaign public needs Premium, VIP, or admin.
rulesetNoRuleset code; list_rulesets returns the codes this account can use. Becomes the campaign's first leg. Play enforces required and a known code on the backend (400) and answers 403 for a ruleset this account is not entitled to; the gateway lets it be omitted so the LLM gets a clean backend error if it forgets.
summaryNoShort campaign summary. Max 150 characters.
descriptionNoFull campaign description. Markdown supported.
hideSectionsNo
xCardEnabledNo
autoRollInitiativeNoWhether a token placed on the campaign's battlemaps gets its initiative rolled (a d20 plus its character's initiative bonus) when it joins the initiative order. Only tokens backed by a character in a ruleset with an initiative roll are rolled; every other token joins unscored. A battlemap rolls only when every one of its campaigns has this on. On by default.
showCreatureDetailsNoWhether players see a creature's details (its health and armor class, per ruleset) at the top of a token's details on the campaign's battlemaps. A battlemap shows them only when every one of its campaigns has this on. Off by default.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • addedInput schema / properties / autoRollInitiative
      Added value: +{
      +  "description": "Whether a token placed on the campaign's battlemaps gets its initiative rolled (a d20 plus its character's initiative bonus) when it joins the initiative order. Only tokens backed by a character in a ruleset with an initiative roll are rolled; every other token joins unscored. A battlemap rolls only when every one of its campaigns has this on. On by default.",
      +  "type": "boolean"
      +}
    • addedInput schema / properties / hideSections / properties / items
      Added value: +{
      +  "type": "boolean"
      +}
    • addedInput schema / properties / hideSections / properties / moves
      Added value: +{
      +  "type": "boolean"
      +}
    • addedInput schema / properties / hideSections / properties / partyOrder
      Added value: +{
      +  "type": "boolean"
      +}
    • addedInput schema / properties / hideSections / properties / spells
      Added value: +{
      +  "type": "boolean"
      +}
  2. Changed1 schema field changed
    • addedInput schema / properties / showCreatureDetails
      Added value: +{
      +  "description": "Whether players see a creature's details (its health and armor class, per ruleset) at the top of a token's details on the campaign's battlemaps. A battlemap shows them only when every one of its campaigns has this on. Off by default.",
      +  "type": "boolean"
      +}
  3. Changed3 schema fields changed
    • removedInput schema / properties / active
      Removed value: -{
      -  "type": "boolean"
      -}
    • changedInput schema / properties / public / description
      Previous value: -"Whether non-members can see the campaign."New value: +"Whether non-members can see the campaign. Making the campaign public needs Premium, VIP, or admin."
    • removedInput schema / properties / sessions
      Removed value: -{
      -  "items": {
      -    "description": "Mongo `_id` reference (24-character hex string).",
      -    "minLength": 1,
      -    "type": "string"
      -  },
      -  "type": "array"
      -}
  4. Changed3 schema fields changed
    • changedInput schema / properties / ruleset / description
      Previous value: -"Ruleset code (e.g. '5th Edition', '5e24', 'PFRPG', 'Savage Worlds'). Becomes the campaign's first leg. Play enforces required on the backend; the gateway lets it be omitted so the LLM gets a clean backend error if it forgets."New value: +"Ruleset code; list_rulesets returns the codes this account can use. Becomes the campaign's first leg. Play enforces required and a known code on the backend (400) and answers 403 for a ruleset this account is not entitled to; the gateway lets it be omitted so the LLM gets a clean backend error if it forgets."
    • removedInput schema / properties / ruleset / enum
      Removed value: -[
      -  "5th Edition",
      -  "5e24",
      -  "PFRPG",
      -  "PFRPG2",
      -  "PF Playtest",
      -  "Savage Worlds",
      -  "Savage Embers",
      -  "Solarian Conflict",
      -  "Embers RPG",
      -  "Universal",
      -  "Fate Core",
      -  "Fate Accelerated"
      -]
    • addedInput schema / properties / ruleset / minLength
      Added value: +1
  5. Changed13 schema fields changed
    • addedInput schema / $schema
      Added value: +"http://json-schema.org/draft-07/schema#"
    • addedInput schema / additionalProperties
      Added value: +{}
    • addedInput schema / properties / active
      Added value: +{
      +  "type": "boolean"
      +}
    • addedInput schema / properties / description
      Added value: +{
      +  "description": "Full campaign description. Markdown supported.",
      +  "type": "string"
      +}
    • addedInput schema / properties / hideSections
      Added value: +{
      +  "additionalProperties": {},
      +  "properties": {
      +    "characters": {
      +      "type": "boolean"
      +    },
      +    "logistics": {
      +      "type": "boolean"
      +    },
      +    "players": {
      +      "type": "boolean"
      +    },
      +    "rules": {
      +      "type": "boolean"
      +    },
      +    "safetyTools": {
      +      "type": "boolean"
      +    },
      +    "sessionZero": {
      +      "type": "boolean"
      +    },
      +    "sessions": {
      +      "type": "boolean"
      +    }
      +  },
      +  "type": "object"
      +}
    • addedInput schema / properties / image
      Added value: +{
      +  "description": "Image URL. Stored as a plain string.",
      +  "type": "string"
      +}
    • addedInput schema / properties / name
      Added value: +{
      +  "description": "Campaign name. Required.",
      +  "minLength": 1,
      +  "type": "string"
      +}
    • addedInput schema / properties / public
      Added value: +{
      +  "description": "Whether non-members can see the campaign.",
      +  "type": "boolean"
      +}
    • addedInput schema / properties / ruleset
      Added value: +{
      +  "description": "Ruleset code (e.g. '5th Edition', '5e24', 'PFRPG', 'Savage Worlds'). Becomes the campaign's first leg. Play enforces required on the backend; the gateway lets it be omitted so the LLM gets a clean backend error if it forgets.",
      +  "enum": [
      +    "5th Edition",
      +    "5e24",
      +    "PFRPG",
      +    "PFRPG2",
      +    "PF Playtest",
      +    "Savage Worlds",
      +    "Savage Embers",
      +    "Solarian Conflict",
      +    "Embers RPG",
      +    "Universal",
      +    "Fate Core",
      +    "Fate Accelerated"
      +  ],
      +  "type": "string"
      +}
    • addedInput schema / properties / sessions
      Added value: +{
      +  "items": {
      +    "description": "Mongo `_id` reference (24-character hex string).",
      +    "minLength": 1,
      +    "type": "string"
      +  },
      +  "type": "array"
      +}
    • addedInput schema / properties / summary
      Added value: +{
      +  "description": "Short campaign summary. Max 150 characters.",
      +  "maxLength": 150,
      +  "type": "string"
      +}
    • addedInput schema / properties / xCardEnabled
      Added value: +{
      +  "type": "boolean"
      +}
    • addedInput schema / required
      Added value: +[
      +  "name"
      +]
  6. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already flag a non-readonly, non-idempotent, non-destructive write, so the description adds real value on top by enumerating exactly which fields are persisted at create and that everything else is silently ignored — critical given additionalProperties is open. The entitlement gate for public campaigns is also disclosed. Minor noise: dismissedSessionZeroNudge is listed as written but does not appear in the schema.

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-loaded with the action and the single required parameter, then layered with leg semantics, an explicit write whitelist, and a permission gate in three tight sentences. No filler or restatement of the tool name.

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 10-parameter tool with a nested object and an output schema, the description covers the behaviors an agent could not infer: field whitelisting, leg seeding, invite-driven seats, and the Premium gate. Return shape is correctly left to the output schema; the only gap is the undocumented nested hideSections keys.

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 80%, so the baseline is 3; the description earns an extra point by clarifying that no field outside the whitelist will survive the create call and by reinforcing ruleset's role as the first leg. It does not explain hideSections' nested keys, though the schema leaves those undocumented too.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource plus ownership scope ('Create a new campaign owned by the calling user'), which instantly separates it from play_update_campaign, play_get_campaign and the imagine_create_* siblings. It stops short of naming a competing tool explicitly, so it is clear but not maximally differentiated.

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 concrete routing: ruleset becomes the first leg and further legs go through play_add_campaign_leg, seats come from the invite tools, and going public requires Premium/VIP/admin. No explicit when-not-to-use case, but the alternatives for adjacent operations are named.

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