Skip to main content
Glama

answer

Settles the one popup, leader screen, or deal that question() shows by applying your chosen item, button, or accept/refuse response and returning the outcome or refusal.

Instructions

Answer what the game is asking: settle the one popup, leader screen or deal that question() shows, and nothing else. choice is the answers row's choice: an item's name (a TECH_, UNIT_, BUILDING_, POLICY_, PROMOTION_, BELIEF_ or goody name; liberate / annex / puppet / raze; a dig's choice number), a popup's or leader screen's button number, or on a leader screen accept / refuse (the deal on the table), leave (close it), accept_friendship. args carries the rest the popup needs (a promotion's unit_id, a dig's x and y, a stolen tech's player_id, a religion's beliefs and city). Dispatches on the gate: question() shows which question is up and hands back the rows to copy. It acts on the game as the popup's own button would -- an accepted deal, a razed city, a chosen tech cannot be taken back; a choice the popup does not offer, or an answer when nothing is asked, is refused with {ok: false, err, choices} and nothing happens. action_id: a retry with the same token replays the stored reply instead of answering twice. Not this tool: a decision with no popup up (research, production, a policy) is order; what a choice means is reference. Returns {ok, ...} with the popup's outcome and the gate that follows (still_pending and next when another leader waits; next also names the call that resumes the AIs' round when they are still moving), or the refusal.

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

Input Schema

NameRequiredDescriptionDefault
argsNowhat the popup needs beyond the choice: unit_id, x and y, player_id, beliefs, city
choiceYesthe `answers` row's choice: an item name, a button number, or accept / refuse / leave / accept_friendship
action_idNoa token of my choosing: a retry with the same action_id replays the stored result

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv2.1.0

TDQS

A4.7/5.0
Behavior4/5

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

Goes well past the annotations: it discloses irreversibility ("an accepted deal, a razed city, a chosen tech cannot be taken back"), the refusal contract ({ok: false, err, choices} with nothing happening), and the action_id replay semantics for retries. The only friction is that destructiveHint=false sits oddly beside an irreversible city razing, and the idempotency token is the sole guard against double-answering, which the description does at least surface.

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 action and the scope, then the choice vocabulary, then effects, then the refusal contract and routing. Dense and long, with heavy parentheticals and semicolon-chained clauses, but nearly every clause supplies decision-relevant information rather than restating the schema.

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?

There is no output schema, and the description still explains the return value ({ok, ...} with the popup's outcome plus still_pending and next), the failure shape, and the follow-up call when AIs are still moving. Combined with the discovery pointer to question() and the sibling routing, an agent has everything needed to invoke it correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is already 100%, yet the description still adds the value space: choice is an item name (TECH_, UNIT_, BUILDING_, POLICY_, PROMOTION_, BELIEF_ or goody), liberate/annex/puppet/raze, a dig choice number, a button number, or accept/refuse/leave/accept_friendship; args carries unit_id, x and y, player_id, beliefs, city. No enum exists in the schema, so this text is the only place those legal values are defined.

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?

"Answer what the game is asking: settle the one popup, leader screen or deal that question() shows" states a specific verb and a tightly bounded scope. It also names the things it acts on (popup, leader screen, deal) so the agent can tell it apart from batch/order/turn without reading 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?

Explicit routing is given in both directions: use question() to discover what is pending, and "Not this tool: a decision with no popup up (research, production, a policy) is order; what a choice means is reference." That names the alternatives and the condition that selects them.

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