Skip to main content
Glama

turn

Manage a Civilization V seat: check status or briefing, run queued actions, end the current round, and wait until play returns to you.

Instructions

The clock: my seat's turn loop, one action per call. Actions: status -- whose turn it is, the gate (answer it before anything else), what blocks the end. Read-only. briefing -- my turn in one read: decisions with their actions rows, changes, board, threats, notes. finish -- run actions as a batch, end my turn, wait until it is mine again, return the new turn. end -- end the turn only, no wait. wait -- block until it is my turn again. Arguments by action: since, limit and detail belong to briefing (since='turn' after a context reset; detail='digest' is the event digest alone); actions and notes to finish; timeout_seconds to finish and wait; args (skip_quiet_turns, wake_on, autosave, force, briefing) to finish and end. Side effects: finish and end hand the game to the other players, and nothing they do can be undone -- order and answer everything first; a session save is the way back. finish autosaves to the quick-save slot. A refused row in actions stops the batch and the turn is not ended. Safe to repeat: when it is not my turn, finish only waits. A second client of my seat is refused with turn_claim (args.force takes the turn over). Timeouts: past timeout_seconds (600 by default) the reply says my_turn false, timed_out true and next is the call that resumes the wait; progress notifications go out every 5 s meanwhile, so one long call beats several short ones. Not this tool: question / answer for what the game asks (nothing ends while gate is set); state for the board; batch for orders that leave the turn open; session for saves. Returns: turn, my_turn, gate, todo / decisions, digest (what happened meanwhile), notes; game_over with victory / defeat at the end. A refusal is {ok: false, err, end_turn: {todo, skip_actions}}: what blocks the turn and the rows that clear it.

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

Input Schema

NameRequiredDescriptionDefault
argsNofinish / end only, by name: skip_quiet_turns (a count: keep ending turns, up to N more, while nothing needs you), wake_on (words that stop a quiet run), autosave (default true), force (take the turn over from another client of my seat), briefing (finish: the new turn as a briefing)
limitNobriefing: rows per list of changes and notes (default 8)
notesNofinish: which notebook notes ride on the reply, 'new' (default) or 'all'
sinceNobriefing: 'previous' (default) compares with my last briefing, 'turn' with the last turn end (after a context reset)
actionYesstatus | briefing | finish | end | wait
detailNobriefing: 'compact' (default) or 'digest' (the event digest alone)
actionsNofinish only: order rows to run before the turn ends, [{tool, args}] as the reads hand them back
timeout_secondsNofinish / wait: seconds to wait for my turn before answering with the state so far (default 600)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.7.1
    • changedInput schema / properties / args / description
      Previous value: -"other arguments of the old call by name: skip_quiet_turns (a count: keep ending turns, up to N more, while nothing needs you), wake_on, autosave, briefing"New value: +"finish / end only, by name: skip_quiet_turns (a count: keep ending turns, up to N more, while nothing needs you), wake_on (words that stop a quiet run), autosave (default true), force (take the turn over from another client of my seat), briefing (finish: the new turn as a briefing)"
  2. Changed1 schema field changedv2.7.0
    • changedInput schema / properties / args / description
      Previous value: -"other arguments of the old call by name: skip_quiet_turns, wake_on, autosave, briefing"New value: +"other arguments of the old call by name: skip_quiet_turns (a count: keep ending turns, up to N more, while nothing needs you), wake_on, autosave, briefing"
  3. Addedv2.1.0

TDQS

A4.8/5.0
Behavior5/5

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

The description goes well beyond the annotations: which actions are read-only ('status -- Read-only'), which are irreversible ('nothing they do can be undone -- order and answer everything first; a session save is the way back'), that finish autosaves, that a refused row aborts the batch, that the call is safely repeatable when it isn't my turn, and the timeout/notification cadence. None of that is inferable from destructiveHint=false or 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?

Front-loaded with the core purpose, then organized into actions, arguments-by-action, side effects, timeouts, not-this-tool, and returns. It is long but tele squash-dense and mostly earns its length; a couple of parenthetical clauses could be tightened, which is why it's not a 5.

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?

With no output schema, the description still documents returns ('turn, my_turn, gate, todo / decisions, digest, notes; game_over with victory / defeat') and even the refusal shape ('{ok: false, err, end_turn: {todo, skip_actions}}'). Combined with the side-effect and timeout coverage, an agent has everything needed to call it correctly.

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 baseline 3 applies, but the description adds per-action routing that is not in the schema: 'since, limit and detail belong to briefing; actions and notes to finish; timeout_seconds to finish and wait; args (...) to finish and end.' This meaningfully reduces misfires on which param pairs with which action.

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 ('the clock: my seat's turn loop, one action per call') and then enumerates each of the five actions with a one-line purpose. This differentiates the tool from siblings like question, state, batch, and session without the agent having to open 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 Guidelines5/5

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

Explicitly names alternatives in 'Not this tool: question / answer for what the game asks; state for the board; batch for orders that leave the turn open; session for saves,' plus the key exclusion that nothing ends while gate is set. This is exactly the when/when-not routing an agent needs.

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