Skip to main content
Glama

Diplomacy report

eu5_diplomacy

Retrieve a country's overlord, subjects and their liberty desire, diplomatic record, and active wars from an EU5 save to assess its political and military standing.

Instructions

Overlord, subjects (with liberty desire), the country's diplomacy record, and wars it is in.

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

Input Schema

NameRequiredDescriptionDefault
saveNoSave to use: "latest", a file name like "autosave.eu5", or a full path. Defaults to the last loaded save, else the newest.
countryNoCountry tag (e.g. SWE), numeric country id, or name. Defaults to the player's country.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.6/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden and discloses only the data categories returned. It never states that this is a read-only, side-effect-free query, nor how the save/country defaults resolve at runtime, nor anything about output size for a country with many subjects and wars.

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?

One compact sentence with no filler, and the most distinctive element (liberty desire) is surfaced early. But the telegraphic fragment style omits a subject and verb, making it read like a field list rather than a statement of what the tool does.

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

Completeness3/5

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

For a two-optional-parameter read query with no output schema, enumerating the returned sections is reasonably helpful. Still missing is any signal of read-only safety, overlap with eu5_wars, or how the per-country scoping interacts with the default country.

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 description coverage is 100% and both parameters are optional with documented fallback behavior ("latest"/file/path, tag/id/name). The description adds no parameter meaning beyond the schema, so the baseline of 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names the resource and enumerates its contents (overlord, subjects with liberty desire, diplomacy record, wars), which is more specific than the title alone. However, it is a bare noun phrase with no verb, so an agent must infer that it *returns* a report rather than modifying diplomacy. No sibling is named or implicitly contrasted, even though eu5_wars and eu5_country_overview overlap in scope.

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

Usage Guidelines2/5

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

There is no guidance on when to call this versus eu5_wars (which presumably covers war data) or eu5_country_overview. No prerequisites, no exclusions, no mention of which country is reported by default beyond what the schema already states.

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