Skip to main content
Glama

Province report

eu4_provinces

Lists your country's owned provinces with development, trade goods, culture/religion mismatches, cores, autonomy and devastation so you can spot uncored land and plan development or conversion.

Instructions

Owned provinces with development, trade goods, culture/religion mismatches, cores, autonomy, devastation, buildings, occupation. Also lists uncored provinces and trade-good totals.

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

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.
sortNodevelopment
limitNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations, the description bears the full behavioral burden. It does disclose scope behavior worth knowing (owned provinces plus a separate list of uncored provinces and trade-good totals), but it omits that this is a read-only report, how the result is truncated (the limit default/max live only in the schema), and what the player-country default means for output size. That leaves real gaps for a tool with zero annotation coverage.

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?

Two sentences, no filler, and the content list is front-loaded. The comma-separated field dump is dense but appropriate for a report tool. Slight deduction for reading as an unstructured inventory rather than a directive statement of purpose.

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 and no annotations, the description does carry the return-field inventory reasonably well, which is its main strength. However it says nothing about result ordering, truncation by limit, or how uncored provinces and trade-good totals are structured within the response. Adequate but with clear gaps for a 4-parameter report tool.

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?

The description never mentions tag, save, sort, or limit, so it adds no parameter meaning beyond the schema. Coverage is 50%: tag and save are well documented in-schema, and the sort enum values are self-descriptive, which limits the damage. Baseline 3 is the fair ceiling since the description itself contributes nothing here.

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 concrete resource (provinces) and enumerates the exact data returned: development, trade goods, culture/religion mismatches, cores, autonomy, devastation, buildings, occupation, plus uncored provinces and trade-good totals. An agent can distinguish this province-level report from country-level siblings such as eu4_country_overview or eu4_economy. It falls short of a 5 because there is no verb and no explicit sibling differentiation.

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 mention of alternatives such as eu4_economy or eu4_find_problems. The only implied usage is 'inspect province data', which the agent must infer from the field list. No exclusions or selection criteria are given.

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