Skip to main content
Glama

Load an EU4 save

eu4_load_save

Parses EU4 save files, including compressed and ironman saves, and returns a campaign summary with date, player, version, DLCs, mods and headline stats. Later tools reuse this save by default.

Instructions

Parse a save (text, compressed, or ironman via rakaly) and return a campaign summary: date, player, version, DLCs, mods and the player's headline stats. Later tools reuse this save by default.

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

Input Schema

NameRequiredDescriptionDefault
fullNoParse everything including province histories and trade (slower, more memory). Only needed for eu4_query on skipped sections.
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

A4.2/5.0
Behavior4/5

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

With no annotations, the description carries the burden and does real work: it names accepted input formats (text, compressed, ironman via rakaly) and discloses that loading mutates shared session state that later tools inherit by default. It does not cover failure modes such as a missing or unreadable save, which keeps it from a 5.

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?

Two sentences, no redundancy, with the core action and its outputs front-loaded and the workflow note reserved for the end. Every clause earns its place.

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?

Without an output schema, the description compensates by enumerating the returned summary fields and the accepted formats, which is enough for an agent to know what it gets back. The remaining gap is error/edge-case behavior for invalid or absent saves, minor for a read-oriented parse tool.

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%, so both parameters are already documented in the schema, including the 'latest'/filename/path resolution and the full-parse cost. The description's state-reuse sentence reinforces the `save` default behavior but adds no syntax or format detail beyond what the schema states.

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

Purpose5/5

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

States a specific verb and resource ('Parse a save') and enumerates exactly what comes back: date, player, version, DLCs, mods, headline stats. The clause 'Later tools reuse this save by default' also positions it relative to the rest of the toolset, so an agent can tell this is the setup step rather than a query.

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

Usage Guidelines4/5

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

The final sentence communicates the intended workflow — load once here, then subsequent tools operate on the loaded save — which is the key when-to-use signal. It stops short of explicit exclusions (e.g. 'use eu4_list_saves to discover files first'), so it is clear context rather than full routing guidance.

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