Skip to main content
Glama

Raw country record

eu5_country_raw

Dumps a country's raw save records to a chosen depth, revealing fields the standard reports omit. Use it to inspect uncovered data like economy sub-paths.

Instructions

Depth-limited raw dump of a country's record in the save, for fields the reports don't cover.

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

Input Schema

NameRequiredDescriptionDefault
saveNoSave to use: "latest", a file name like "autosave.eu5", or a full path. Defaults to the last loaded save, else the newest.
depthNo
countryNoCountry tag (e.g. SWE), numeric country id, or name. Defaults to the player's country.
sectionNoOptional sub-path inside the country, e.g. 'economy'.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.7/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 burden. It does disclose that output is 'depth-limited' and 'raw' (i.e., unstructured/complete record data), which hints at payload size and fidelity, but it says nothing about read-only safety, output size limits, stability of the raw structure, or how depth affects verbosity beyond the number.

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 no filler: the operation, its scoping, and its intended use all arrive in order. Every word earns its place.

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 4-parameter raw-export tool with no annotations, no output schema, and an undocumented 'depth' parameter, the description is adequate but thin. It never characterizes the return shape (raw JSON structure, how section nesting interacts with depth), which is exactly what an agent needs before calling a 'raw dump'.

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 75% with save, country, and section well documented, so the baseline is 3. The description contributes only the notion that the dump is 'depth-limited', loosely tying the undocumented 'depth' parameter to output verbosity, but it adds no format or interpretation detail for country tags or section paths.

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?

Names a concrete verb+resource ('raw dump of a country's record in the save') and adds a scoping clause ('for fields the reports don't cover') that implicitly separates it from report-style siblings like eu5_country_overview or eu5_economy. It stops short of naming any sibling explicitly, so the differentiation is inferred rather than stated.

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?

'For fields the reports don't cover' gives a clear selection rule: this is the fallback when structured report tools lack a field. It provides context for when to reach for it but offers no explicit exclusion or a named preferred alternative to try first, so an agent must infer the ordering.

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