Skip to main content
Glama

send_diplomatic_action

Sends a diplomatic action to another civilization by player ID, including delegation, friendship, denouncement, embassy, open borders, or war declaration.

Instructions

Send a proactive diplomatic action to another civilization.

Args:
    other_player_id: The player ID (from get_diplomacy output)
    action: One of: DIPLOMATIC_DELEGATION, DECLARE_FRIENDSHIP, DENOUNCE,
            RESIDENT_EMBASSY, OPEN_BORDERS,
            DECLARE_SURPRISE_WAR, DECLARE_FORMAL_WAR, DECLARE_HOLY_WAR,
            DECLARE_LIBERATION_WAR, DECLARE_RECONQUEST_WAR,
            DECLARE_PROTECTORATE_WAR, DECLARE_COLONIAL_WAR,
            DECLARE_TERRITORIAL_WAR
    force: Override the pre-war gate (NO_SIEGE_VS_WALLS). War declarations
    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.
           against a civ with visible walled cities are blocked while you
           have no wall-breaker units (siege class, battering ram/siege
           tower, or ranged strength >= 60).

Delegations cost 25 gold and can be rejected if the civ dislikes you.
Embassies require Writing tech. Use get_diplomacy to see available actions.
Surprise war is always available if not allied/friends. Other war types
(casus belli) require specific civics and conditions.

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

Input Schema

NameRequiredDescriptionDefault
forceNo
actionYes
force_reasonNo
other_player_idYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden and does supply real behavior: delegation cost of 25 gold, rejection risk, Writing tech requirement for embassies, surprise-war availability, and the pre-war gate plus force_log recording. The pre-war gate paragraph is garbled and out of order ('against a civ with visible walled cities are blocked while you have no wall-breaker units' appears after the force_reason note), which obscures the key rule. Solid content, damaged by scrambled structure.

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

Conciseness2/5

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

The force/force_reason block is visibly mangled: the gate explanation is split and spliced after the force_reason sentence with misplaced indentation, so sentences run together out of logical order. Elsewhere the prose is dense and useful, but the ordering failure actively hurts comprehension of the most safety-relevant parameter.

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. For a 4-param, zero-schema-coverage mutation tool, the description covers parameter meanings, costs, tech prerequisites, and the war-gate exception — nearly everything an agent needs, short of sibling routing.

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 0%, so the description must compensate and does: it explains other_player_id's provenance ('from get_diplomacy output'), enumerates all 13 action values (the schema has no enum at all), and explains both force (overriding the NO_SIEGE_VS_WALLS gate) and force_reason (recorded to data/force_log.jsonl). This is well beyond what the schema provides.

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?

Opens with a specific verb+resource ('Send a proactive diplomatic action to another civilization') and the word 'proactive' distinguishes it from respond_to_diplomacy. It never names a sibling explicitly, so an agent must infer the boundary itself.

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

Usage Guidelines3/5

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

'Use get_diplomacy to see available actions' gives a discovery path, and the war-type rules hint at when certain actions are legal. However, there is no guidance on when NOT to use this versus respond_to_diplomacy or get_pending_diplomacy, which are the obvious confusable siblings.

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