Skip to main content
Glama

Active wars

eu4_wars

Lists active wars from an EU4 save, optionally filtered by country tag, including sides, war goals, participant contributions and losses, and recent battles.

Instructions

All active wars (or only those involving a country): sides, war goal, participants' contribution and losses, recent battles.

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

Input Schema

NameRequiredDescriptionDefault
tagNoOnly wars involving this tag. Omit for all wars.
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

A3.5/5.0
Behavior3/5

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

With no annotations supplied, the description carries the full behavioral burden; it does disclose the shape of the returned data (sides, war goal, contributions, losses, battles), which is genuinely helpful. It does not state that the operation is read-only, how large the output may be, or what happens when no wars are active or the save is unspecified.

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?

It is a single compact sentence with the scope stated first and the return contents listed after the colon, so nothing is buried. The telegraphic fragment style is dense but slightly terse, which costs it a point.

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?

This is a simple read-style query with two optional, fully documented parameters and no output schema, and the description compensates for the missing output schema by listing the fields returned. Only minor gaps remain, such as default behavior when no save is loaded.

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 both the tag and save parameters are already documented with omit/default semantics in the schema. The description only echoes the tag filter concept ('or only those involving a country') and adds no syntax or format detail 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 and scope ('All active wars', optionally filtered to one country) and enumerates the returned content (sides, war goal, contributions, losses, recent battles). It is clear what the tool does, though it does not explicitly distinguish itself from overlapping siblings such as eu4_military or eu4_diplomacy.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The parenthetical 'or only those involving a country' implies when to supply the tag filter, which is useful usage context. However, there is no explicit when-to-use vs. when-to-prefer-another-tool guidance, and no mention of prerequisites such as needing a loaded save.

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