Skip to main content
Glama

History trends

eu4_trends

Retrieve yearly ledger history for a country's income, size, score, and inflation from EU4 saves to analyze campaign trends and compare economic growth.

Instructions

Yearly history of a country's income, size, score and inflation recorded by the game ledger since the campaign start.

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_trends"
  }
}

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?

With no annotations, the description must carry the behavioral load; it does disclose the meaningful constraint that data comes from the game ledger and only begins at campaign start, which implies earlier years may be absent. It does not say whether the call is read-only, what happens if the ledger has gaps, or how many rows/years to expect.

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 that front-loads the resource and then lists the metrics; nothing is padded. It could be marginally tighter, but there is no wasted wording to cut.

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 simple two-parameter read tool with full schema coverage and no output schema, the description adequately names the returned series and its origin. The only real gap is granularity/pagination and behavior on missing years, which is minor at this complexity level.

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%, with both 'tag' and 'save' fully documented including their defaults, so the schema already does the explanatory work. The description adds nothing about the parameters—no note on what happens when tag is omitted (player country) or on save resolution—so the baseline 3 applies.

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 states a specific resource (yearly history/trends) and enumerates the exact metrics returned: income, size, score and inflation. An agent can tell it is a time-series view rather than a snapshot, though it does not name a sibling to contrast with (e.g. eu4_economy for current state).

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 phrase 'yearly history ... since the campaign start', which suggests reaching for this when multi-year progression matters. There is no explicit when-to-use vs. when-not guidance, no mention of how it differs from eu4_economy or eu4_compare_saves, and no stated prerequisites such as a loaded save.

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