Skip to main content
Glama

Compare countries

eu4_compare_countries

Compare multiple countries from an EU4 save side by side to assess development, economy, technology, manpower, armies, navies, and stability.

Instructions

Side-by-side comparison of several countries (development, economy, tech, manpower, army, navy, stability…).

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": {
      "tags": "<tags>"
    },
    "name": "eu4_compare_countries"
  }
}

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.
tagsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.7/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden and does not meet it: it never states that this is a read-only operation, whether a save must be loaded first, or what happens when a tag is invalid or the save is missing. The only disclosed trait is the set of metrics compared, which is scope rather than behavior.

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 filler; the parenthetical metric list is efficient. It is under-specified rather than verbose, so length is not the problem.

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?

With no annotations, no output schema, and an undocumented required 'tags' parameter, the description does not cover enough for an agent to invoke the tool confidently. It should at minimum explain the tag format and confirm the read-only, save-scoped nature of the call.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 50%: the 'save' parameter is documented in the schema, but 'tags' has no schema description and no mention in the tool description beyond the vague phrase 'several countries'. An agent cannot tell from the description that tags are the country identifiers, what format they take, or that 1–10 are allowed.

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 uses a specific verb+resource ('Side-by-side comparison of several countries') and enumerates the compared dimensions (development, economy, tech, manpower, army, navy, stability). It does not distinguish itself from siblings like eu4_country_overview or eu4_rankings, which also surface country stats, so the boundary is left implicit.

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?

The description says nothing about when to reach for this tool versus eu4_country_overview (single country), eu4_rankings, or eu4_query. Usage is only inferable from the word 'comparison'; no prerequisites, exclusions, or alternatives are named.

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