Skip to main content
Glama

Country overview

eu4_country_overview

Get a country's headline state from an EU4 save: ruler and heir stats, government, tech, monarch points, treasury, loans, stability, prestige, manpower, army and navy size, subjects and wars.

Instructions

Headline state of a country: ruler/heir stats, government, tech, monarch points, ideas, treasury & balance, loans, stability, prestige, war exhaustion, overextension, manpower, army/navy size, subjects and wars.

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

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

B3.2/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. It lists returned data categories but does not state that the operation is read-only, how defaults are resolved beyond the schema, or what errors or response structure to expect.

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?

The description is a single front-loaded sentence with a colon introducing the returned fields. The long comma-separated list is dense but every item contributes to defining what the overview includes.

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 no output schema, the description usefully lists the broad return categories and the fully documented schema covers both parameters. However, it omits explicit guidance versus the many specialized sibling tools and does not disclose read-only behavior or default resolution in prose.

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?

Both optional parameters, tag and save, have full schema descriptions, so the schema already carries their meaning. The description adds no additional parameter syntax, defaults, or constraints beyond what the schema provides, which matches the baseline for complete schema coverage.

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 resource, a country's headline state, and enumerates the exact data categories returned. It is clearly an overview tool rather than a specialized sibling, though it never explicitly names alternatives like eu4_economy or eu4_military.

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?

The word "headline" implies using this for a quick summary instead of detailed sibling tools, but there is no explicit when-to-use guidance, no exclusions, and no named alternatives. Usage is inferable rather than stated.

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