Skip to main content
Glama

List EU4 saves

eu4_list_saves

List EU4 save files newest first with date, player country, version, ironman flag, and size to quickly find the save you want to inspect or compare.

Instructions

List EU4 save files (newest first) with date, player country, version, ironman flag and size.

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

Input Schema

NameRequiredDescriptionDefault
dirNoExtra folder to scan.
limitNo

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?

With no annotations, the description must carry the behavioral burden. It usefully discloses sort order (newest first) and the exact result fields, which implies a read-only scan, but it says nothing about whether the scan is recursive, where the default location is, or how large directories 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence with no filler; the ordering and returned-field list are packed in tightly and every clause carries information an agent needs.

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?

For a read-only, zero-required-parameter list tool with no output schema, enumerating the returned fields is the right use of the description. The remaining gap is the default scan location and interaction with dir, which an agent would need to predict results.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 50%, and the description adds nothing about either parameter. It never explains what dir actually does (an extra folder on top of an implied default) or that limit caps the number of returned saves, leaving the reader dependent on a terse schema description.

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?

States a specific verb and resource ("List EU4 save files") and enumerates the fields returned (date, player country, version, ironman flag, size) plus the ordering (newest first). This clearly separates it from siblings like eu4_load_save or eu4_compare_saves, though it never names an alternative explicitly.

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 use this tool versus eu4_load_save, eu4_compare_saves, or eu4_search. No prerequisites, no exclusions, no mention of what happens when no saves exist or when dir is omitted.

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