Skip to main content
Glama

respond_to_diplomacy

Respond to a pending diplomacy encounter from another civilization by sending a POSITIVE or NEGATIVE response. Automatically handles multi-round conversations and closes when dialogue ends.

Instructions

Respond to a pending diplomacy encounter.

Args:
    other_player_id: The player ID of the other civilization (from get_pending_diplomacy)
    response: "POSITIVE" (friendly) or "NEGATIVE" (dismissive)

First meetings typically have 2-3 rounds. The tool automatically detects
and closes goodbye-phase sessions (where dialogue text stops changing).
If SESSION_CONTINUES is returned, send another response for the next round.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
responseYes
other_player_idYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior5/5

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

No annotations provided, so description carries full burden. Discloses that the tool automatically closes goodbye-phase sessions and returns SESSION_CONTINUES to indicate more rounds. This reveals stateful behavior beyond the schema.

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

Conciseness5/5

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

Description is concise with a clear first line, structured Args section, and additional behavioral notes. Every sentence provides value; no redundant or vague phrasing.

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?

Covers essential details: usage, parameters, multi-round behavior, and auto-detection. Minor gap: does not explain what happens with invalid input or other possible return values beyond SESSION_CONTINUES. Otherwise complete for a two-parameter tool.

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 has no descriptions (0% coverage). Description adds full meaning: 'other_player_id' is the player ID from get_pending_diplomacy, 'response' is 'POSITIVE' or 'NEGATIVE' with friendly/dismissive mapping. Completely compensates for missing schema descriptions.

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?

Clearly states the tool responds to a pending diplomacy encounter. Provides specific verb ('respond') and resource ('diplomacy encounter'). Distinguishes from siblings like 'get_diplomacy' and 'propose_peace' by focusing on active response.

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 says when to use (pending encounter from get_pending_diplomacy) and how to interpret response values ('POSITIVE' or 'NEGATIVE'). Describes multi-round behavior and auto-detection of goodbye sessions, giving clear context for iterative use.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/wrislin1/civ6-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server