Skip to main content
Glama

Wars

eu5_wars

Extract wars from a Europa Universalis V save, including start dates, sides, war score, and battles, and optionally filter for wars involving a specified country.

Instructions

Wars in the save (or involving a country): start date, sides, war score where present, 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": "eu5_wars"
  }
}

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.
countryNoOnly wars involving this 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 burden. It does disclose the shape of the returned data (sides, war score where present, battles) and the "where present" caveat usefully signals missing fields, but it says nothing about result size, grouping, or default save resolution beyond what the schema already states.

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 with the resource front-loaded and the optional filter relegated to a parenthesis. No filler, though the fragmentary style with a bare colon list is slightly clipped rather than fully readable.

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 simple two-parameter read tool with no output schema, the description gives a reasonable field inventory (start date, sides, war score, battles). It stops short of explaining how multiple wars are returned or what happens with no matching wars, leaving minor gaps.

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 parameters are already documented in the schema, including the save-resolution defaults and the country filter. The description's "in the save (or involving a country)" only restates that country acts as an involvement filter, adding no syntax or format detail.

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 (wars) and enumerates the returned fields: start date, sides, war score, battles. It is clear this is a read/list tool over war data, though the verb is implicit and no sibling tool is named to sharpen the boundary (e.g., versus eu5_diplomacy or eu5_query).

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?

The parenthetical "(or involving a country)" hints at the optional filter, but there is no explicit when-to-use guidance, no when-not-to-use, and no alternative tool is referenced. An agent must infer from the name and siblings that this is the war-listing endpoint.

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