Skip to main content
Glama

Detect EU5 setup

eu5_environment

Detects your operating system, save folders, game install and version, language, and rakaly availability so EU5 save analysis works on Windows, Linux, or macOS.

Instructions

Detect OS (EU5 is Windows-native; Linux via Proton, macOS via CrossOver/Whisky), save folders, game install + version, language and rakaly availability.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

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?

No annotations are provided, so the description bears the full burden. It usefully discloses the platform variations (Windows-native, Linux via Proton, macOS via CrossOver/Whisky) and that rakaly availability is probed, which tells the agent this may behave differently per host. It does not say whether the tool errors out when the game or saves are missing, how long detection takes, or whether it writes anything.

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 compact sentence with the primary action front-loaded and no filler. The parenthetical OS detail is dense but each clause maps to a distinct detected item, so nothing is wasted.

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?

With no output schema, the description must indicate what comes back, and it does so by enumerating the detected items: OS, save folders, install path and version, language, and rakaly status. The remaining gap is failure or partial-detection behavior, which leaves the caller unprepared for a missing install or empty save directory.

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

Parameters4/5

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

The tool takes zero parameters, so the baseline is 4 and there is nothing the description needs to disambiguate. The description correctly implies a no-argument probe rather than leaving the caller searching for inputs.

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 verb 'Detect' plus the resource 'EU5 setup' is specific, and the description enumerates exactly what is detected: OS, save folders, game install and version, language, and rakaly availability. That set clearly separates it from data-oriented siblings such as eu5_list_saves and eu5_load_save, though it never explicitly contrasts itself with them.

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 statement of when to call this tool, whether it should be run before other eu5_* tools, or what alternatives exist for the information it returns. The 'Detect' framing hints that it is a setup/precondition check, but the caller must infer that.

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