Skip to main content
Glama

Read an EU5 wiki page

eu5_wiki_page

Fetches an EU5 wiki page as plain text so you can look up game mechanics and answer campaign questions with reliable reference information.

Instructions

Fetch an EU5 wiki page as plain text (truncated).

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": {
      "title": "<title>"
    },
    "name": "eu5_wiki_page"
  }
}

Input Schema

NameRequiredDescriptionDefault
titleYes
maxCharsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.7/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. It discloses that output is plain text and truncated, which is useful, but says nothing about truncation mechanics relative to maxChars, what happens if the title does not exist, whether the wiki is fetched over the network, or any rate/latency concerns.

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?

One short, front-loaded sentence with no wasted words. It is arguably too terse for a tool with an undocumented schema, but nothing in it is padding.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No annotations, no output schema, and 0% parameter description coverage mean the description is the only source of semantics, and it supplies almost none of what is needed: title format, truncation behavior, and failure modes are all absent.

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, and the description mentions neither 'title' (e.g., exact page name, case sensitivity, spaces vs underscores) nor 'maxChars' (default 12000, max 40000). 'Truncated' only faintly gestures at the maxChars parameter.

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 ('Fetch') and resource ('an EU5 wiki page') plus the output format ('as plain text'). It does not explicitly distinguish itself from the sibling eu5_wiki_search, leaving the search-vs-fetch relationship to inference from the names.

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 guidance on when to use this tool versus eu5_wiki_search, no statement of prerequisites, and no note on how a page title is obtained (presumably from a prior search). The agent must guess the workflow.

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