Skip to main content
Glama

Military report

eu4_military

Inspect a country's armies, navies, manpower, traditions, and professionalism, then compare military strength against rivals and current enemies from an EU4 save.

Instructions

Armies (regiments by infantry/cavalry/artillery, strength, morale, location), navies, manpower, traditions, professionalism, and a strength comparison against rivals and current enemies.

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

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

C2.9/5.0
Behavior2/5

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

No annotations exist, so the description carries the full behavioral burden. It usefully enumerates what the report contains (partially compensating for the missing output schema), but never says the operation is read-only, what happens if no save is loaded, or whether scope defaults to the player's country.

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 sentence that front-loads the most important content (armies) and wastes no words. It reads as a content list rather than a sentence with a subject and verb, but that suits a report tool.

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?

For a two-optional-parameter read tool with no output schema, the content enumeration does real work by telling the agent what data comes back. However, relative to its sibling set it leaves out usage routing and any statement about safety or save-state assumptions.

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% for both optional parameters (tag, save), so the schema already explains the country tag format and the save resolution order. The description adds no filtering or parameter semantics beyond that, which is the expected baseline when the schema does the heavy lifting.

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 enumerates a concrete resource set — army regiments broken down by infantry/cavalry/artillery with strength, morale and location, plus navies, manpower, traditions, professionalism, and rival/enemy strength comparison. That specificity makes it distinguishable from eu4_economy or eu4_diplomacy, though the verb is only implied by the title 'Military report' rather than stated in the description.

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 guidance on when to choose this over siblings such as eu4_country_overview, eu4_compare_countries, or eu4_wars, all of which plausibly overlap on force comparison. It also doesn't state a prerequisite like a loaded save, leaving the agent to infer the context.

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