Skip to main content
Glama

Search the EU5 wiki

eu5_wiki_search

Search the official Europa Universalis V wiki for mechanics, buildings, laws, and other game details to answer campaign questions.

Instructions

Search the official Europa Universalis V wiki (eu5.paradoxwikis.com) for mechanics, buildings, laws, etc.

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": {
      "query": "<query>"
    },
    "name": "eu5_wiki_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
queryYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden, and all it really discloses is that the source is an external wiki at a named domain. It says nothing about whether results are snippets or full pages, how many come back beyond the undocumented limit, whether the call depends on network availability, or any rate limiting.

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?

A single compact sentence with the resource and domain front-loaded; nothing is padded. The trailing 'etc.' slightly weakens precision about scope but costs almost no space.

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?

For a low-complexity two-parameter search tool with no output schema, the description covers the 'what' adequately. It falls short on return-value shape and query semantics, which matter more here precisely because there is no output schema to fall back on.

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 two parameters, so the description must compensate, and it does not — neither 'query' nor 'limit' is mentioned. The agent gets no hint about query syntax (keyword vs. phrase), expected granularity, or what the limit means in practice (default 8, max 20).

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?

Names a specific verb (Search) and a specific resource (the official Europa Universalis V wiki), including the exact domain, so the agent knows this queries external wiki content rather than save-game data. It is distinguishable in spirit from eu5_search and eu5_wiki_page, though it never names or contrasts them explicitly.

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 phrase 'for mechanics, buildings, laws, etc.' implies the kind of lookups this suits, giving an agent a rough sense of when to reach for it. However, there is no explicit when-not guidance and no mention of eu5_wiki_page as the natural follow-up for opening a specific article, so routing must be inferred.

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