Skip to main content
Glama

World rankings

eu4_rankings

Rank all living countries in an EU4 save by development, income, manpower, army, treasury, provinces, prestige, great power score, tech, or debt, and see where the player stands.

Instructions

Rank all living countries by a metric and show where the player stands.

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

Input Schema

NameRequiredDescriptionDefault
saveNoSave to use: "latest" (newest save on disk), a file name like "autosave.eu4", or a full path. Defaults to the last loaded save, else the newest.
limitNo
metricNodevelopment

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/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 burden; "Rank ... and show" does convey a read-only reporting operation and adds a real behavioral detail that only living countries are included, which the schema does not state. It says nothing about ordering direction, truncation by limit, or whether a save must be loaded first, so the safety profile is only implied by the verb.

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 front-loaded sentence with no wasted words. Its brevity is efficient rather than padded, though the terseness is part of why parameters go unexplained.

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?

For a three-parameter, low-coverage, no-output-schema tool, the description leaves too much open: ordering direction, what the limit controls, and what the returned ranking rows look like are all unspecified. An agent could invoke it, but not predict whether it gets the top N, the bottom N, or the player's neighborhood.

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 only 33%: the save parameter is documented in the schema and merely echoed conceptually here, while metric and limit are undocumented. "By a metric" gestures at the metric enum without explaining the choices or that results are ordered by it, and the limit parameter (default 15, max 100) is never addressed despite "rank all" implying full-set ranking.

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 ("Rank") and resource ("all living countries") plus a secondary output (the player's standing), which reads clearly against comparison siblings like eu4_compare_countries. It stops short of explicitly naming an alternative, so differentiation is inferable rather than stated.

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?

The description only implies when to use it: you want an ordered list by a metric. It gives no explicit when-not conditions, no mention of when to prefer eu4_compare_countries or eu4_country_overview instead, and no prerequisites (such as needing a save loaded).

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