Skip to main content
Glama

order

Destructive

Execute state-changing Civilization V actions such as unit moves, city production, diplomacy, and spy missions; use action_id to retry without acting twice.

Instructions

An order to something I own: to the target kind, id which one, action the verb, args its arguments by name. It changes the game, and most of it cannot be undone (a disbanded unit, a declared war, a purchase). Not a read: state shows the board and hands back the rows, question / answer settle what a popup asks, turn(action='finish') ends the turn. to: actions -- unit: move, mission, promote, upgrade, disband, trade_route, plunder city: produce, purchase, dequeue, sell_building, buy_plot, specialist, work_plot, governor, status, strike, great_work empire: research, policy, ideology, switch_ideology, pantheon, religion, enhance_religion, reformation, faith_purchase civ: propose_deal, negotiate, peace, demand, friendship, declare_war, denounce, event city_state: gift_gold, gift_unit, gift_improvement (or a city-state screen button by its name: pledge, revoke_pledge, bully_gold, bully_unit, declare_war, make_peace) league: propose, repeal, vote spy: move, coup How: copy the rows a read hands back (actions, call) as they are; id is a unit, city, civ, city-state or spy id (empire and league take none); args holds what the row holds (a plot's x and y, an item's name, a deal's items, an amount). An order runs whole or not at all. action_id: a token of mine; a retry with the same one replays the stored reply instead of acting twice. Returns {ok: true, ...} with what changed (a unit's new plot and moves left, a city's queue, a deal's answer), or {ok: false, err, choices / accepts, example}: the verb is not one of the target's (choices lists them), an argument is missing (accepts names the shape, example a complete call), or the game refuses it (err names the rule, e.g. the unit has no moves, the city is not mine, another client of my seat holds this turn's claim). Nothing is acted on when ok is false.

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": {
      "to": "<to>",
      "action": "<action>"
    },
    "name": "order"
  }
}

Input Schema

NameRequiredDescriptionDefault
idNowhich unit, city, civ, city-state or spy; empire and league take none
toYesthe target kind, something I own
argsNothe action's arguments by name, as the copied row has them; a refusal shows the shape with an example
actionYesthe verb, by target -- unit: move, mission, promote, upgrade, disband, trade_route, plunder; city: produce, purchase, dequeue, sell_building, buy_plot, specialist, work_plot, governor, status, strike, great_work; empire: research, policy, ideology, switch_ideology, pantheon, religion, enhance_religion, reformation, faith_purchase; civ: propose_deal, negotiate, peace, demand, friendship, declare_war, denounce, event; city_state: gift_gold, gift_unit, gift_improvement, or a city-state screen button by its name (pledge, revoke_pledge, bully_gold, bully_unit, declare_war, make_peace); league: propose, repeal, vote; spy: move, coup
action_idNoa token of my choosing: a retry with the same action_id replays the stored result instead of acting twice

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv2.1.0

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already declare `destructiveHint=true` and `readOnlyHint=false`; the description adds that most changes cannot be undone with concrete examples such as disbanding a unit or declaring war. It also discloses all-or-nothing execution, detailed failure returns, and `action_id` replay semantics, which is a useful idempotency-key nuance rather than a contradiction of `idempotentHint=false`.

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?

The definition is front-loaded and structured, placing purpose and alternatives before action details and return behavior. It is long and repeats the action enum already present in the schema, but the density is largely justified by the tool's breadth.

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?

No output schema exists, so the description's return-shape explanation is necessary and complete: it covers `{ok: true, ...}` changed state and `{ok: false, err, choices / accepts, example}` failures. It also explains atomicity and error cases, making the definition self-contained 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 description coverage is 100% and the schema already documents and enumerates `to` and `action`. The description adds operational meaning beyond the schema: copy the read's returned rows for `id` and `args`, `action_id` replays stored replies, and empire/league targets take no `id`.

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 opening sentence defines an order as a mutation on something I own and names the core fields `to`, `id`, `action`, and `args`. The action lists map verbs to target kinds, and the description explicitly distinguishes this tool from read/query siblings.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It explicitly says 'Not a read' and routes board reading to `state`, popup resolution to `question` / `answer`, and turn ending to `turn(action='finish')`. It also explains how to construct calls by copying rows returned by reads and that an order executes atomically.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools