Skip to main content
Glama

Campaign health check

eu5_find_problems

Scan a Europa Universalis V save for economic, military, and stability problems such as deficits, loans, low manpower, occupation, and multi-front wars, with advice to fix them.

Instructions

Find problems and opportunities (deficit, negative gold, loans, stability, prestige, manpower, low control, untapped tax, market access, occupation, multi-front wars) with advice.

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

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.
countryNoCountry tag (e.g. SWE), numeric country id, or name. Defaults to the player's country.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.4/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 usefully discloses the analysis surface (which conditions are detected) and that output includes "advice", but never states that the operation is read-only/non-mutating, nor whether it evaluates the loaded save, which save it reads, or how findings are returned. Enough behavioral context to be usable, not enough to be safe-by-description.

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: purpose first, then the parenthetical enumeration of checks, then the "with advice" output hint. Zero preamble or restatement; the long list is dense but every item conveys a distinct detectable condition, so it earns its space.

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?

With only two optional, fully documented parameters and no output schema or annotations, the main gaps are behavioral: no statement of whether it is read-only, what the advice output looks like, or how it interacts with the loaded save. The enumerated check list covers the analytical scope well, making it adequate but not complete.

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 optional parameters (save, country) are fully documented in the schema with their defaults, so the description needs to add nothing. It does add nothing about them, which is acceptable at this coverage level but earns only the baseline.

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 ("Find") and a clearly scoped resource ("problems and opportunities") and enumerates the concrete check categories it covers (deficit, loans, stability, manpower, market access, etc.), so an agent knows this is a diagnostic/audit tool rather than a raw data dump like eu5_country_overview. It stops short of explicitly contrasting itself with any sibling.

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: the enumerated checks and the title "Campaign health check" suggest running it to triage a campaign, but there is no statement of when to prefer it over eu5_country_overview, eu5_economy, or eu5_compare_saves, and no prerequisites or exclusions. An agent must infer the routing.

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