Skip to main content
Glama

Campaign health check

eu4_find_problems

Scans an EU4 country for problems and missed opportunities—deficits, loans, inflation, low stability, overextension, tech gaps, rebels, succession—and returns concrete advice sorted by severity.

Instructions

Scan a country for problems and missed opportunities (deficits, loans, inflation, low stability, overextension, wasted monarch points, empty idea slots, tech gaps, low manpower, rebels, estates, succession…) with concrete advice, sorted by severity.

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

Input Schema

NameRequiredDescriptionDefault
tagNoCountry tag (e.g. FRA, TUR) or name. Defaults to the player's country.
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.

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 are supplied, so the description carries the full burden. It does disclose return behavior — diagnoses paired with concrete advice, ordered by severity — which tells the agent the output is prescriptive rather than raw data. It does not state that the operation is read-only, whether it depends on a currently loaded save, or how expensive a full scan is, leaving gaps for a tool with zero annotation coverage.

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 that leads with the verb and resource before sprawling into the parenthetical category list. The enumeration is long but each item is a distinct detectable problem, so it earns its space; the trailing 'with concrete advice, sorted by severity' usefully closes with output shape.

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?

The tool is a broad read-only scanner with no output schema, and the description compensates by naming the problem classes it reports and how they are ordered. It stops short of describing the result structure (per-problem objects, advice format) or the cost of a full scan, but nothing essential for invoking it correctly is missing.

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 description coverage is 100% and both parameters (tag, save) are documented there with defaults and example formats. The description adds no additional meaning about tag resolution or save selection, so the schema does all the work; baseline 3 applies.

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?

States a specific verb+resource ("scan a country for problems and missed opportunities") and enumerates the concrete categories it detects — deficits, loans, inflation, stability, overextension, monarch points, idea slots, tech gaps, manpower, rebels, estates, succession. That enumeration plus 'sorted by severity' separates it cleanly from diagnostic siblings like eu4_country_overview or eu4_economy.

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: this is the tool you run for a holistic health check rather than a single-domain view. There is no explicit when-not guidance, no mention of alternatives for narrower questions, and no note on prerequisites such as a loaded save, so an agent must infer routing.

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