Skip to main content
Glama

Raw save lookup

eu5_query

Read any Europa Universalis V save file field by dotted path, such as metadata or countries.tags, to answer campaign questions with real data. Empty path lists top-level sections.

Instructions

Read any field by dotted path, e.g. 'metadata', 'countries.tags', 'war_manager.database.5'. Empty path lists top-level sections.

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

Input Schema

NameRequiredDescriptionDefault
pathNo
saveNoSave to use: "latest", a file name like "autosave.eu5", 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

A3.5/5.0
Behavior3/5

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

With no annotations supplied, the description carries the full burden, and it does establish this is a read operation and discloses the empty-path listing behavior. However it says nothing about what happens when a path does not exist (error vs null), whether lookups are cheap or can be slow on large nested structures, or what the returned shape looks like for a raw field.

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 short sentences, the primary invocation pattern front-loaded, examples grouped compactly, and the empty-path edge case saved for last. No filler and nothing repeated from the schema.

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 three-parameter raw reader with no annotations and no output schema, the definition covers the core path semantics adequately but leaves 'depth' entirely unexplained and gives no error semantics for a bad path. An agent could call it and get a result, but would likely need a second call to understand what depth does.

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 only 33% — the 'save' parameter is documented in the schema while 'path' and 'depth' are not. The description fully compensates for 'path' with syntax and empty-string semantics, but 'depth' (integer, 1–6, default 2) is never mentioned, leaving the agent to guess that it governs how far nested structures are expanded.

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?

States a specific verb and resource — 'Read any field by dotted path' — and backs it with three concrete path examples spanning metadata, a top-level country table, and a nested array index. An agent knows immediately this is a generic raw-save reader rather than a curated view like eu5_country_overview. It stops short of naming when to prefer a sibling, so it lands just below the top mark.

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 implied rather than stated: the empty-path behavior ('lists top-level sections') gives the agent a discovery entry point, and the dotted-path examples imply further drilling. There is no explicit guidance on when to reach for this tool versus eu5_search, eu5_country_raw, or eu5_country_overview, and no stated exclusions or prerequisites.

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