Skip to main content
Glama

Raw save lookup

eu4_query

Read any raw Europa Universalis IV save field by dotted path to inspect countries, provinces, diplomacy, and other game data, returning a depth-limited preview for targeted analysis.

Instructions

Read any raw field by dotted path, e.g. 'countries.FRA.technology', 'provinces.-183', 'diplomacy', 'great_powers'. Returns a depth-limited preview. Use eu4_search to discover paths.

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

Input Schema

NameRequiredDescriptionDefault
pathNoDotted path; empty for top-level keys.
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.
depthNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full disclosure burden. It reveals only that output is a 'depth-limited preview'; it says nothing about what happens on an invalid or missing path, whether a save must be loaded first, whether reads are side-effect free, or whether output is truncated with a marker.

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?

Three short sentences, front-loaded with the capability, then examples, then the return-shape caveat, then the sibling pointer. No filler and nothing buried.

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 single-lookup tool with no output schema and no annotations, the description covers what it reads, example path shapes, and the depth-limited return. The remaining gap is failure behavior on bad paths and the interaction with eu4_load_save, which an agent would otherwise have to discover by trial.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 67% and the undocumented parameter is depth, which the description only indirectly gestures at via 'depth-limited preview' without explaining what a level means. The path examples do add real value beyond 'Dotted path; empty for top-level keys' by showing array-index syntax like 'provinces.-183' that the schema never illustrates.

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?

The description gives a specific verb ('Read') and resource ('any raw field by dotted path'), then grounds it with four concrete path examples spanning nested maps, negative array indices, and top-level keys. It also implicitly separates itself from eu4_search by casting this tool as the retrieval half of a discover-then-read pair.

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?

It names the alternative explicitly ('Use eu4_search to discover paths'), which tells the agent when to reach for that sibling first. It does not state exclusions — e.g. when to prefer eu4_country_overview or eu4_provinces over a raw path read — so the routing is clear but incomplete.

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