Skip to main content
Glama

Diplomacy report

eu4_diplomacy

Review a country's alliances, royal marriages, subjects, rivals, wars, and opinions from an EU4 save to assess diplomatic standing and plan strategy.

Instructions

Alliances, royal marriages, subjects (with liberty desire), overlord, guarantees, rivals and who rivals you, active wars, and the best/worst opinions toward the player's country.

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": "eu4_diplomacy"
  }
}

Input Schema

NameRequiredDescriptionDefault
tagNoCountry tag (e.g. FRA, TUR) or name. Defaults to the player's country.
saveNoSave to use: "latest" (newest save on disk), a file name like "autosave.eu4", or a full path. Defaults to the last loaded save, else the newest.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.5/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. Calling it a 'report' implicitly signals a read-only operation, and the content list tells the agent what data surfaces, but nothing is said about save resolution behavior, side effects, errors when no save is loaded, or response shape.

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?

A single dense sentence with no filler; every listed item corresponds to a real return category. It reads as a bare noun list without a leading clause stating what is being reported for whom, which slightly reduces front-loading.

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?

With no output schema, the description usefully compensates by enumerating the returned sections, including detail like liberty desire and best/worst opinions. Combined with a 100%-covered two-parameter schema, an agent has enough to call it correctly, though default-scoping behavior for tag is left implicit.

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

Parameters3/5

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

Schema coverage is 100% and both optional parameters (tag, save) are fully documented in the schema, so the baseline of 3 applies. The description adds nothing about how tag scoping (country vs. player's country) changes which opinions, rivals, or wars are reported.

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 description enumerates the exact diplomatic entities returned (alliances, royal marriages, subjects with liberty desire, overlord, guarantees, rivals, wars, opinions), which is concrete and lets an agent tell it apart from eu4_wars or eu4_country_overview. It lacks an explicit verb and never states the resource is scoped to one country, but the content list is specific enough to act on.

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?

Usage is only implied by the field list: an agent can infer it is the tool for alliance/vassal/rival/opinion questions, but there is no explicit when-to-use statement and no routing away from siblings such as eu4_wars for pure war data. No preconditions (loaded save, player country context) are mentioned.

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