Skip to main content
Glama

respond_to_trade

Accept or reject a pending trade deal by player ID, with an optional force override and recorded reason for joint-war invitations.

Instructions

Accept or reject a pending trade deal.

Args:
    other_player_id: The player ID of the civilization (from get_pending_trades)
    accept: True to accept the deal, False to reject it
    force: Override the pre-war gate when accepting a joint-war invitation
    force_reason: One sentence on WHY you are overriding. Recorded to
        data/force_log.jsonl. Without it a post-game review cannot tell
        a wrong gate from a wrong call — write it even when in a hurry.
           (NO_SIEGE_VS_WALLS — accepting joint war = declaring war on the
           target immediately)

Use get_pending_trades first to see what's being offered.

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": {
      "other_player_id": "<other_player_id>",
      "accept": "<accept>"
    },
    "name": "respond_to_trade"
  }
}

Input Schema

NameRequiredDescriptionDefault
forceNo
acceptYes
force_reasonNo
other_player_idYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations, the description carries the load and does well: it discloses that force bypasses a pre-war gate, that force_reason is persisted to data/force_log.jsonl, and that accepting a joint war immediately declares war on the target. Reversibility and failure modes are not covered, but the major consequence is surfaced.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The first line is crisply front-loaded, but the force_reason entry sprawls into an admonition about writing it 'even when in a hurry' plus a NO_SIEGE_VS_WALLS parenthetical that actually describes force, not force_reason — misplaced content that muddies which parameter it applies to.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists so return values need not be explained, and the description supplies the prerequisite (get_pending_trades), the consequence of acceptance (war declaration), and the logging side effect. For a state-mutating diplomatic action with no annotations, that is nearly complete, missing only failure/error behavior.

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 description coverage is 0%, so the description must carry all four parameters, and it does: other_player_id is sourced from get_pending_trades, accept is defined as True/False, force is tied to the pre-war gate case, and force_reason has both format (one sentence) and destination (force_log.jsonl). This fully compensates for the empty schema.

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?

States a specific verb pair (accept/reject) on a specific resource (pending trade deal), which clearly separates it from propose_trade, propose_peace and respond_to_diplomacy in the sibling list. It does not explicitly name those siblings, so differentiation is inferable rather than stated.

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?

'Use get_pending_trades first to see what's being offered' gives an explicit prerequisite and names the discovery tool, and the force parameter is scoped to one condition (overriding the pre-war gate on a joint-war invitation). No explicit when-not guidance or mention of respond_to_diplomacy as an alternative.

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