Skip to main content
Glama

Search save keys

eu5_search

Search Europa Universalis V save files for keys or values matching a regex, optionally restricted to a path, to locate campaign data.

Instructions

Find keys (and optionally values) matching a regex, optionally under a path.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "pattern": "<pattern>"
    },
    "name": "eu5_search"
  }
}

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.
limitNo
underNo
valuesNo
patternYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations, the description carries full behavioral burden and discloses little. It notes that values are returned only optionally, which is a mild behavioral hint, but says nothing about regex flavor, case sensitivity, result ordering, truncation at the limit (default 40, max 200), or what happens when the save is missing.

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 wasted words, tightly scoped around verb, mechanism, and optionality. It is arguably over-compressed for a five-parameter tool with thin schema coverage, but nothing is redundant.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a tool with five parameters, 20% schema coverage, no annotations, and no output schema, the definition is too thin. An agent cannot learn the shape of the result (matching keys only vs key/value pairs), how limit interacts with results, or which save is used by default beyond what the 'save' schema note already says.

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 20% (only 'save' is documented), so the description must compensate. It does partially: 'matching a regex' identifies pattern as a regex, 'and optionally values' explains the values flag, and 'under a path' explains the under parameter as a prefix scope. It says nothing about limit semantics or the default-under behavior, leaving real gaps.

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 states a specific verb (find) and resource (save keys, optionally values) plus the matching mechanism (regex) and scope control (under a path), which distinguishes it from siblings like eu5_list_saves or eu5_compare_saves. It does not, however, explicitly contrast itself with eu5_query, which sounds like the nearest alternative.

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

Usage Guidelines2/5

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

There is no when-to-use guidance: nothing says whether this is for exploratory browsing of a save, for locating a known key, or when to prefer eu5_query. 'Optionally under a path' implies a scoping option but is not a usage condition, and no exclusions or prerequisites are given.

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