Skip to main content
Glama

Progress between two saves

eu4_compare_saves

Compare a country between an older and newer save of the same campaign to track changes in development, provinces, income, debt, tech, army, and rank.

Instructions

Compare a country between an older and a newer save of the same campaign (development, provinces, income, debt, tech, army, 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": "eu4_compare_saves"
  }
}

Input Schema

NameRequiredDescriptionDefault
tagNoCountry tag (e.g. FRA, TUR) or name. Defaults to the player's country.
newerNoNewer save (name, path or 'latest').latest
olderYesOlder save (name or path).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.6/5.0
Behavior3/5

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

No annotations exist, so the description carries the full behavioral burden; it does disclose the comparison axes and the same-campaign constraint. It does not clarify the direction/polarity of deltas (older→newer), what happens when campaigns don't match, or how much data comes back, which matters for an unannotated tool.

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?

A single front-loaded sentence with the scope first and the compared metrics parenthesized after it. No filler, no restatement of the title, and the trailing ellipsis economically signals additional untracked metrics.

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?

For a three-parameter read-style tool with no output schema, the description conveys enough: scope, prerequisites, and the dimensions compared. Only failure modes for mismatched saves and the delta direction remain unspecified, which are minor gaps rather than blockers.

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%, so all three parameters (tag, newer, older) already have meaning, including the 'latest' default for newer; baseline is therefore 3. The description adds only the ordering semantics of the two save arguments, without enriching tag resolution or path-vs-name handling beyond what the schema says.

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?

States a specific verb and resource ('Compare a country between an older and a newer save') and enumerates the compared dimensions (development, provinces, income, debt, tech, army, rank), so an agent knows exactly what it returns. It stops short of naming the sibling eu4_compare_countries, which is the obvious near-neighbor, so differentiation is left implicit.

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?

The phrase 'of the same campaign' implies the prerequisite that both saves belong to one campaign, which is genuinely useful selection guidance. However there is no explicit when-to-use / when-not-to-use statement and no pointer to eu4_trends or eu4_compare_countries for cross-country or multi-save comparisons, so usage is only implied.

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