Skip to main content
Glama

question

Read-onlyIdempotent

Reads the game's pending prompt or leader deal and returns ready-to-copy answer calls to settle it. Use when a gate or discussion is pending.

Instructions

What the game is asking right now, so answer() can settle it. Read-only; takes nothing. Use it whenever a reply's gate is not null or turn(action='status') says discussion_pending; use state for the board and reference for the rules. It shows one of: a decision popup (a tech, a production item, a policy, a promotion, a belief, a ruins reward, a captured city's fate, a Great Person's use, a dig), the leader on screen with their words and the deal on the table, another human seat's proposal waiting on the trade table, or nothing pending. Returns the popup's own read -- the question in words plus answers rows, each a complete answer() call to copy (the item's name or button number, and the args the popup needs) -- with gate on the reply; a leader screen returns the leader, the speech, the buttons and the deal's items; when nothing is asked, {pending: false, decisions: [...]} lists the turn's open decisions instead. Several leaders can queue at a turn start: answering one returns the next under next.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "question"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv2.1.0

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already declare readOnlyHint and idempotentHint, so safety is covered; the description goes well beyond them by describing the idle return shape ({pending: false, decisions: [...]}), the leader-screen return contents, and the non-obvious queueing behavior at turn start where answering one leader surfaces the next under `next`. With no output schema present, this return-shape disclosure is exactly the burden the description should carry.

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 core purpose and the trigger condition before the return-shape detail, so an agent can stop reading early. The long parenthetical enumerating every popup type (tech, production item, policy, promotion, belief, ruins reward, captured city, Great Person, dig) is somewhat over-stuffed for the value it adds, keeping it below 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?

There is no output schema, and the description compensates fully by spelling out each return variant, including the empty case and the chained `next` case. Combined with the trigger conditions, an agent has everything needed to call it and interpret the reply 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?

The tool takes zero parameters, so the baseline is 4; the description reinforces this with 'takes nothing', removing any doubt that arguments are required. There is no parameter surface left to explain.

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 opening clause states exactly what is returned — the pending question the game is asking — and enumerates the concrete forms it can take (decision popup, leader screen, human trade proposal, nothing). It actively distinguishes itself from siblings by telling the agent to use state for the board and reference for the rules. A specific verb is implied rather than stated ('What the game is asking ... Read-only; takes nothing'), which keeps it just short of a 5.

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 gives an explicit trigger condition ('whenever a reply's `gate` is not null or turn(action='status') says discussion_pending') and explicit alternatives for the neighbouring concerns ('use state for the board and reference for the rules'). Nothing about when to reach for this tool versus answer/turn/state is left to inference.

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