Skip to main content
Glama

Economy report

eu5_economy

Extract a country's economy from an EU5 save, covering income, taxes, trade, maintenance, loans, and locations with untapped tax for budgeting and expansion decisions.

Instructions

Economy block, every income/tax/trade/maintenance field, loans, and the locations with the most untapped tax.

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

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.2/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 what the response contains (every economy field, loans, top untaxed locations), which is genuine output-shape information, but it never states that this is a read-only operation, how large the response may be, or how the 'most untapped tax' ranking is scoped or ordered.

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 dense clause with zero filler, front-loading the most important content (the economy block) before the detail. The only structural weakness is the lack of a verb, making it read as a label rather than a statement of action.

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?

There is no output schema, so the description must convey return content, and it does so reasonably well by enumerating the field groups. It is still incomplete on scoping (defaults to the player's country) and on the nature of the untapped-tax ranking, which an agent would need to interpret results correctly.

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%, so the schema already explains the save and country parameters, including defaults, in detail. The description adds nothing about them; the baseline of 3 applies.

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 names the resource (the economy block) and enumerates its contents: income/tax/trade/maintenance fields, loans, and locations with the most untapped tax. That is far more specific than the title 'Economy report' alone and lets an agent tell it apart from generic siblings like eu5_country_overview or eu5_country_raw. It loses a point only because it is a bare noun phrase with no verb stating that data is retrieved.

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 prerequisites, and no named alternative among the many siblings (eu5_country_overview, eu5_query, eu5_rankings). The only usage signal is implicit in the listed contents.

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