Skip to main content
Glama

Country overview

eu5_country_overview

Retrieve a country's key stats from an EU5 save—gold, manpower, stability, prestige, income, rank, territory, rulers, and wars—to answer campaign questions with real data.

Instructions

Gold, manpower, stability, prestige, traditions, income/expense, tax & trade, great power rank, territory (locations, control, development), rulers and wars — plus all other scalar fields of the country.

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

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

C2.8/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 burden. It implies a read operation via 'overview' but does not state read-only safety, response size or shape, or cost of a save-wide scan. The one genuine disclosure is 'plus all other scalar fields', which tells the agent the payload is broad but scalar-only — useful, but thin for a no-annotation tool.

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 sentence that front-loads the most-wanted fields (gold, manpower, stability) before the parenthetical detail. The em-dash list is dense but every item is informative; it stays appropriately sized for a summary tool.

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?

With no output schema and no annotations, describing the returned fields is exactly the gap this description should fill, and it does so reasonably completely, including a catch-all for remaining scalar fields. It falls short only in not indicating the response structure (flat object vs. nested sections) or how large the payload may be.

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 coverage is 100% and both parameters document their accepted forms and defaults (save: 'latest'/file/path; country: tag/id/name). The description adds nothing about save or country semantics, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description enumerates the data categories returned (gold, manpower, stability, territory, rulers, wars) which makes the resource clear, but it never states the action — whether this fetches, computes, or summarizes — relying on the title 'Country overview' to do that work. It also gives no signal distinguishing it from siblings such as eu5_country_raw, eu5_economy, or eu5_wars, which appear to cover overlapping subsets.

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?

There is no when-to-use guidance, no exclusions, and no mention of alternatives. With siblings like eu5_country_raw and eu5_economy present, an agent has to guess whether this broad overview is preferable to a narrower or rawer sibling.

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