Skip to main content
Glama

Progress between two saves

eu5_compare_saves

Compare a country's gold, income, manpower, stability, prestige, locations, control, and rank between an older and newer EU5 save to track campaign changes.

Instructions

Compare a country between an older and a newer save (gold, income, manpower, stability, prestige, locations, control, rank).

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": {
      "older": "<older>"
    },
    "name": "eu5_compare_saves"
  }
}

Input Schema

NameRequiredDescriptionDefault
newerNolatest
olderYes
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.8/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 burden. It implies a read-only diff and reveals the compared metrics, which is useful given there is no output schema, but it never says what happens with an invalid save name, that 'newer' defaults to the latest save, or how missing metrics are handled.

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 front-loaded sentence with no filler; the parenthetical metric list is dense but earns its place by previewing the diff output. Slightly list-heavy but well structured.

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 3-parameter read-only comparison with no output schema, the metric enumeration partially substitutes for return documentation. However, the default behavior for 'newer' and the source of valid save names are left unstated, which an agent needs in order to call it correctly.

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

Parameters2/5

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

Schema description coverage is only 33%, so the description should compensate. It does map vaguely onto 'older' and 'newer', but never explains that 'newer' defaults to 'latest' nor how save identifiers are obtained; only 'country' is documented, and that is in the schema, not the description.

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 gives a specific verb ('compare') and resource ('a country between an older and a newer save') and even enumerates the metrics compared (gold, income, manpower, stability, prestige, locations, control, rank). This is clear enough to distinguish it from siblings like eu5_country_overview or eu5_country_raw, though it never explicitly names those alternatives.

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 explicit when-to-use guidance, no mention of prerequisites (both saves must exist and be named as in eu5_list_saves), and no routing to alternatives such as eu5_country_raw for a single-save snapshot. The comparison framing implies usage, but nothing is stated.

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