Skip to main content
Glama

Economy report

eu4_economy

Analyze income, expenses, loans, inflation, and corruption from an EU4 save to diagnose budget issues and guide economic strategy.

Instructions

Last month's income/expense breakdown (taxation, production, trade, army maintenance …) with percentages, last year totals, lifetime spending, loans with interest, inflation and corruption.

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

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
Behavior3/5

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

No annotations are supplied, so the description carries the behavioral burden. It does usefully disclose the shape of the returned data (breakdown with percentages, year totals, lifetime spending, loans with interest, inflation, corruption), but it never states that the tool is read-only, whether the 'save' parameter causes a save to be loaded or mutated in server state, or how missing countries/saves are handled.

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 efficient sentence that front-loads the core resource ('income/expense breakdown') before enumerating fields. The trailing ellipsis ('…') is the only imprecision, hinting at unaudited additional content.

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?

The tool is simple (two optional parameters, no output schema), and the description partially compensates for the absent output schema by listing the returned content categories. However, the ellipsis leaves the field set open-ended, and nothing covers defaults, units, or failure modes for an unfamiliar tag or save.

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%, with both 'tag' and 'save' fully documented including defaults and format examples. The description adds no parameter-level meaning beyond that, so 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 a specific resource (last month's income/expense breakdown) and enumerates the exact content categories returned (taxation, production, trade, army maintenance, loans, inflation, corruption). It is clear which question this tool answers, though the verb is only implied by the title 'Economy report' and no sibling is named for contrast.

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 explicit when-to-use or when-not-to-use guidance. An agent can infer from the name and content list that this is the economy lookup rather than eu4_military or eu4_diplomacy, but nothing states the conditions under which this tool should be preferred over eu4_country_overview or eu4_trends for economic data.

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