Skip to main content
Glama

Locations report

eu5_locations

Retrieve owned locations with development, control, prosperity, tax vs possible tax, market access, raw material, settlement rank, religion, and occupation, plus averages and counts.

Instructions

Owned locations with development, control, prosperity, tax vs possible tax, market access, raw material, settlement rank, religion and occupation; plus averages and counts.

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": "eu5_locations"
  }
}

Input Schema

NameRequiredDescriptionDefault
saveNoSave to use: "latest", a file name like "autosave.eu5", or a full path. Defaults to the last loaded save, else the newest.
sortNodevelopment
limitNo
countryNoCountry tag (e.g. SWE), numeric country id, or name. Defaults to the player's country.

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?

No annotations are supplied, so the description carries full behavioral burden. It notes that the report includes averages and counts, but does not disclose read-only status, pagination, default sort/limit behavior, or what data is returned beyond the field list.

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 semicolon-separated sentence front-loads the subject and field list. It is compact, though the field list is dense and the phrase 'tax vs possible tax' is slightly opaque.

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?

With four parameters, no annotations, no output schema, and only 50% schema coverage, the definition is underpowered. It does not describe return structure, pagination, defaults, or read-only behavior, leaving meaningful gaps for an agent.

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?

The schema documents save and country, but sort and limit have no schema descriptions. The description lists some sortable fields, but it does not explain the sort parameter, limit, defaults, or allowed values, so it fails to compensate for the 50% schema coverage.

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 specifies the resource and enumerates output fields such as development, control, prosperity, tax vs possible tax, market access, raw material, settlement rank, religion, and occupation. It lacks a verb and does not distinguish the tool from siblings like eu5_country_overview or eu5_country_raw, but the resource is identifiable.

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?

No guidance is given on when to use this report versus country_overview, country_raw, rankings, or search. The only implicit scope is 'owned locations' and the country parameter defaulting to the player's country, but no alternatives or exclusions are named.

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