Skip to main content
Glama

List EU5 saves

eu5_list_saves

List .eu5 saves newest first with in-game date, country, version, and format to find and compare campaign files.

Instructions

List .eu5 saves newest first with in-game date, country, version and format (text/binary).

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

Input Schema

NameRequiredDescriptionDefault
dirNo
limitNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.1/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 full behavioral burden. It usefully discloses sort order ('newest first') and the shape of each returned row, but says nothing about pagination beyond the schema's limit, whether subdirectories are scanned, or what happens when no saves exist or the directory is invalid.

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 sort order and returned fields are packed in without wasted words. Nothing could be removed without losing information.

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, the description does well to name the fields returned, which partially covers the return-value gap. However, for a listing tool with an undocumented 'dir' parameter and a capped result set, the omission of default location and truncation/pagination behavior leaves an agent guessing about coverage of 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 0% for both parameters, and the description compensates for neither. It never explains what 'dir' means (a save folder? a game install path? a default when omitted?) or that 'limit' caps results with a default of 15 and a maximum of 100.

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 gives a specific verb and resource ('List .eu5 saves') and even enumerates the fields each entry carries (in-game date, country, version, text/binary format). It does not differentiate itself from siblings such as eu5_compare_saves or eu5_load_save, so it stops short of a 5.

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 or when-not-to-use guidance and no mention of prerequisites such as which directory is searched by default. The agent must infer that this is the discovery step before eu5_load_save or eu5_compare_saves, which is plausible but never stated.

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