Skip to main content
Glama

Search save keys

eu4_search

Search EU4 save files with case-insensitive regex to find keys or values anywhere or under a specific path, such as countries.FRA. Use it to locate data without manually scanning the save.

Instructions

Find keys (and optionally values) matching a regex anywhere in the save, optionally under a path (e.g. under='countries.FRA').

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": "eu4_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
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.
limitNo
underNo
valuesNoAlso match scalar values.
patternYesCase-insensitive regular expression.

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, the description carries the full burden. It does disclose the matching model (regex, case-insensitivity via schema, matching both keys and scalar values, optional path scoping), which is the core behavior, but it says nothing about the shape of results, ordering, truncation at the default limit of 40, or what happens when no save is loaded.

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?

One sentence, front-loaded with the action and resource, with the two modifiers introduced in the order an agent would apply them. Nothing is redundant or padded.

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?

A five-parameter search tool with no annotations and no output schema needs more than one sentence. The description never says what a match looks like (key path, value, both?), how results are limited or ordered, or what the caller should expect when the regex matches nothing, leaving the agent to guess at the return contract.

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?

Coverage is 60% and the description compensates well for the gap: 'under' has no schema description, yet the example under='countries.FRA' conveys the dotted path syntax, and 'optionally values' explains what the values flag turns on. Only 'save' and 'limit' are left entirely to the schema, where they are already documented.

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 ('Find keys (and optionally values)') and scopes it precisely to a regex search 'anywhere in the save', optionally narrowed by a path. An agent can immediately tell this is an exploratory text/path search over raw save structure rather than a structured query, though no sibling (e.g. eu4_query) is named for contrast.

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: 'anywhere in the save, optionally under a path' suggests this is the tool for locating unknown keys or paths, and the 'under' option implies narrowing once a path is known. There is no explicit when-to-use / when-not-to-use statement and no named alternative such as eu4_query for structured lookups.

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