Skip to main content
Glama

Update the campaign

world_update

Applies changes to a Plot Speaks campaign's saved world: new characters, damage and healing, spells cast, items, gold, rests, location, day, people met (the dead stay dead), quests, fight turn order (initiative) and a one-line story note. Send only what changed; fields left out are untouched. Returns a RECORDED list, a REFUSED list giving the reason for each change the campaign's rules do not allow, and the updated state. Saves to the campaign play (no personal data). An unknown slug, a non-campaign story or an unknown play id returns an error. Call it silently: never say "let me check", "let me check on that", "one moment" or "hang on" before or after, and never mention the tool.

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": {
      "slug": "<slug>",
      "play_id": "<play_id>"
    },
    "name": "world_update"
  }
}

Input Schema

NameRequiredDescriptionDefault
dayNoThe campaign day number, e.g. 3, if it moved on
noteNoOne line for the story so far (kept to 240 characters)
npcsNoPeople met or changed, each {name, status, note}; status e.g. friendly, hostile or dead (the dead stay dead); notes kept to 160 characters. E.g. [{"name":"Old Bram","status":"friendly"}]
restNo"short" or "long": applies that rest's recovery to the party under the campaign's rules
slugYesThe campaign's slug or title, e.g. the campaign named in start_story's script
partyNoUp to 6 party members to add or change, matched by name (an unknown name adds a character). Each: name, plus any of class, level (1 to 5), hp, max_hp, damage, heal, spend_slot (spell level 1 to 5), max_slots, conditions, add_items, remove_items, gold (the new total, never a change: 30 gold plus 20 found is gold 50), remove. E.g. [{"name":"Mira","damage":4,"spend_slot":"1"}]
questsNoQuests taken or changed, each {name, status, note}; status is open, done or failed; notes kept to 160 characters. E.g. [{"name":"Find the lantern","status":"done"}]
play_idYesThe campaign's play id from start_story or world_recall, e.g. 3f2b8c1e-9d4a-4e7b-a1c2-5b6d7e8f9a0b
locationNoWhere the party is now, e.g. the Sunken Chapel (kept to 120 characters)
initiativeNoThe turn order in a fight, first is up, naming only creatures the party can see (the screen shows it), e.g. ["Mira","Goblin","Tobin"]; sending the list again replaces it, and an empty list ends the fight

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / party / description
      Previous value: -"Up to 6 party members to add or change, matched by name (an unknown name adds a character). Each: name, plus any of class, level (1 to 5), hp, max_hp, damage, heal, spend_slot (spell level 1 to 5), max_slots, conditions, add_items, remove_items, gold (change, may be negative), remove. E.g. [{\"name\":\"Mira\",\"damage\":4,\"spend_slot\":\"1\"}]"New value: +"Up to 6 party members to add or change, matched by name (an unknown name adds a character). Each: name, plus any of class, level (1 to 5), hp, max_hp, damage, heal, spend_slot (spell level 1 to 5), max_slots, conditions, add_items, remove_items, gold (the new total, never a change: 30 gold plus 20 found is gold 50), remove. E.g. [{\"name\":\"Mira\",\"damage\":4,\"spend_slot\":\"1\"}]"
  2. Changed9 schema fields changed
    • changedInput schema / properties / day / description
      Previous value: -"The campaign day, if it moved on"New value: +"The campaign day number, e.g. 3, if it moved on"
    • changedInput schema / properties / initiative / description
      Previous value: -"The turn order in a fight, first is up, naming only creatures the party can see (the screen shows it); send it again as the turn moves on, and an empty list when the fight ends"New value: +"The turn order in a fight, first is up, naming only creatures the party can see (the screen shows it), e.g. [\"Mira\",\"Goblin\",\"Tobin\"]; sending the list again replaces it, and an empty list ends the fight"
    • changedInput schema / properties / location / description
      Previous value: -"Where the party is now (kept to 120 characters)"New value: +"Where the party is now, e.g. the Sunken Chapel (kept to 120 characters)"
    • changedInput schema / properties / npcs / description
      Previous value: -"People met or changed (status e.g. friendly, hostile, dead; notes kept to 160 characters)"New value: +"People met or changed, each {name, status, note}; status e.g. friendly, hostile or dead (the dead stay dead); notes kept to 160 characters. E.g. [{\"name\":\"Old Bram\",\"status\":\"friendly\"}]"
    • changedInput schema / properties / party / description
      Previous value: -"Changes to party members, by name (a new name adds a character)"New value: +"Up to 6 party members to add or change, matched by name (an unknown name adds a character). Each: name, plus any of class, level (1 to 5), hp, max_hp, damage, heal, spend_slot (spell level 1 to 5), max_slots, conditions, add_items, remove_items, gold (change, may be negative), remove. E.g. [{\"name\":\"Mira\",\"damage\":4,\"spend_slot\":\"1\"}]"
    • changedInput schema / properties / play_id / description
      Previous value: -"The campaign play id"New value: +"The campaign's play id from start_story or world_recall, e.g. 3f2b8c1e-9d4a-4e7b-a1c2-5b6d7e8f9a0b"
    • changedInput schema / properties / quests / description
      Previous value: -"Quests taken or changed (notes kept to 160 characters)"New value: +"Quests taken or changed, each {name, status, note}; status is open, done or failed; notes kept to 160 characters. E.g. [{\"name\":\"Find the lantern\",\"status\":\"done\"}]"
    • changedInput schema / properties / rest / description
      Previous value: -"A short or long rest"New value: +"\"short\" or \"long\": applies that rest's recovery to the party under the campaign's rules"
    • changedInput schema / properties / slug / description
      Previous value: -"The campaign's slug"New value: +"The campaign's slug or title, e.g. the campaign named in start_story's script"
  3. First observed

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, openWorldHint=false and idempotentHint=false, so the safety profile is covered. The description adds genuine context beyond that: it discloses the RECORDED/REFUSED return structure, that the campaign's rules can reject individual changes with reasons, that state persists to the campaign play with no personal data, and that initiative re-sends replace the list while an empty list ends the fight. Some of this is valuable, but the description does not address the non-idempotent hint directly for other fields, so it does not fully earn a 4-5.

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?

It is front-loaded with the purpose, then behavior, then error cases, then a calling directive -- a sensible order. The enumeration of affected fields largely mirrors the schema, and the silent-call clause lists four near-synonymous example phrases ('let me check', 'let me check on that', 'one moment', 'hang on'), which is slightly padded.

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 10-parameter mutation tool with no output schema, the description covers what is needed: what it changes, that changes are partial, what is returned (recorded vs refused with reasons), persistence, and error conditions. An agent has enough to call it correctly without opening 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 description coverage is 100%, so the baseline is 3. The description's one semantic contribution is the partial-update rule ('send only what changed'), which reframes every parameter as an optional delta, but it does not elaborate on the trickier semantics (gold as a new total, initiative replacement) that the schema already handles.

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?

The description opens with a specific verb and resource ('Applies changes to a Plot Speaks campaign's saved world') and then enumerates the affected domains: characters, damage/healing, spells, items, gold, rests, location, day, NPCs, quests, initiative and note. It is unmistakably a campaign-state mutation tool. It does not, however, explicitly contrast itself with the read-oriented sibling world_recall, so an agent must infer the write-vs-read split.

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 a concrete operational rule -- 'Send only what changed; fields left out are untouched' -- plus explicit failure conditions (unknown slug, non-campaign story, unknown play id). What it lacks is an explicit routing statement such as 'call world_recall first to read state; use world_update only to change it', so the when-not-to-use case is left implicit.

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