Skip to main content
Glama

Explain a mechanic

eu4_explain

Explains EU4 mechanics such as overextension, aggressive expansion, or stability with tips and a wiki link, helping you understand game concepts and plan strategy.

Instructions

Short explanation + tips for an EU4 mechanic (overextension, aggressive expansion, stability, war exhaustion, inflation, corruption, monarch points, ideas, development, trade, institutions, manpower, autonomy, estates, loans) with a wiki link.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "topic": "<topic>"
    },
    "name": "eu4_explain"
  }
}

Input Schema

NameRequiredDescriptionDefault
topicYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.7/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description carries the full behavioral burden. It usefully states that the output is a short explanation plus tips and a wiki link, but it does not say how unsupported topics are handled or whether the information is static versus save-dependent.

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?

The definition is a single front-loaded sentence with no wasted framing. The long parenthetical topic list is purposeful, though it makes the sentence dense.

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 simple one-parameter explainer with no output schema, the description gives adequate scope and output expectations. It remains slightly incomplete on topic matching behavior and unsupported-topic handling, but nothing critical is missing.

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 coverage is 0%, so the single 'topic' parameter is undocumented in the schema. The description compensates by listing many supported topic names, which adds meaningful guidance, but it does not specify exact formatting, case sensitivity, or whether arbitrary topics are accepted.

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?

The description uses a specific verb, 'explain,' and a specific resource, 'EU4 mechanic,' then lists the supported mechanics. This clearly distinguishes it from the data-query and analysis siblings.

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

Usage Guidelines3/5

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

The topic list implies when the tool is useful, but there is no explicit when-to-use, when-not-to-use, or alternative routing. An agent can infer that it is for mechanics explanations rather than save queries, but the guidance is only implicit.

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