Skip to main content
Glama

Load an EU5 save

eu5_load_save

Parse Europa Universalis V save files, including binary saves via rakaly, and return a campaign summary with the player's snapshot for real-data campaign answers.

Instructions

Parse a save (plaintext natively, binary via rakaly) and return a campaign summary with the player's snapshot.

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

Input Schema

NameRequiredDescriptionDefault
fullNoAlso parse histories/flags (slower).
saveNoSave to use: "latest", a file name like "autosave.eu5", 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

B3.4/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 whole burden; it does disclose the parsing paths (plaintext natively, binary via rakaly) and the return shape, which are real behavioral facts not derivable from schema. It omits failure modes for a bad path, any cost/size limits, and never explicitly confirms the operation is read-only and non-mutating of the save.

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, and the format-handling parenthetical is compact rather than rambling. It is well sized for the amount of information conveyed, though it packs two distinct facts (input formats, return payload) into one clause without separation.

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?

There is no output schema and no annotations, so the description is the only place a caller can learn what comes back; it names 'campaign summary' and 'player snapshot' but gives no indication of the fields or size of that summary. For a two-parameter read tool that is borderline adequate, but the missing return detail leaves a real gap.

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 fully documented, including the 'full' slowness caveat and the 'latest'/filename/path forms with their default fallback. The description adds no parameter meaning beyond that, so 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 gives a specific verb (parse/load) and resource (an EU5 save file) and states the outcome: a campaign summary plus the player's snapshot. It is clear what the tool does, but it never names a sibling to differentiate itself from, so an agent cannot tell from this text alone why it should pick this over eu5_list_saves or eu5_compare_saves.

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: the tool reads as the natural entry point before country/economy/war queries, but the description never says when to use it, when not to, or which alternative takes over. The default-resolution behavior for the save parameter lives in the schema rather than being reinforced as guidance here.

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