Skip to main content
Glama

Detect EU4 setup

eu4_environment

Detects your OS, EU4 save and install folders, game version, language, and rakaly CLI availability; run it first when save files can't be found.

Instructions

Detect OS, EU4 user/save folders, game install + version, language, and whether the rakaly CLI (needed for ironman saves) is available. Call this first if saves can't be found.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.2/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 burden and does add real context: it discloses that the rakaly CLI is a prerequisite for ironman saves, which explains a failure mode. It still does not state whether the probe is strictly read-only, whether it writes any config, or how long a scan may take.

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?

Two compact sentences: the first enumerates what is detected, the second gives the routing condition. The trigger is front-loaded in imperative form and no sentence is filler.

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 zero-parameter diagnostic with no output schema, the description effectively previews the return contents by listing OS, folders, version, language, and CLI availability. Only the shape/format of the result and any failure cases are left implicit.

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 there is nothing for the schema to describe and nothing for the description to clarify; the baseline of 4 applies. No parameter-level gaps exist.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Names a specific verb ("Detect") plus an enumerated set of resources: OS, user/save folders, install path and version, language, and rakaly CLI availability. It is unmistakably a setup/diagnostics probe, distinct from the analytical siblings like eu4_load_save or eu4_list_saves.

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

Usage Guidelines4/5

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

Gives one explicit trigger: "Call this first if saves can't be found," which tells the agent when to reach for it. It does not say whether to run it preemptively at session start or how it relates to eu4_list_saves / eu4_load_save, so guidance is clear but not exhaustive.

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