Statesman MCP Server

get_country

Retrieve a sovereign country's full profile—continent, thematic statecraft tags, and strategic cities—by ID for geopolitical analysis and comparative research.

Instructions

Retrieve full profile of a sovereign country including continent, thematic statecraft tags, and strategic cities.

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": {
      "id": "<id>"
    },
    "name": "get_country"
  }
}

Input Schema

Name	Required	Description
`id`	Yes	Country ID
`include_cities`	No	Include strategic cities belonging to this country
`include_embedding`	No	Include raw 1024-dim vector embedding

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Nov 13, 2026

TDQS

A3.5/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. "Retrieve" does imply a read-only operation and the description names the returned sections, but it omits error behavior for a missing/invalid ID and gives no hint about the cost or size implications of requesting the 1024-dim embedding.

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 well-formed sentence with no filler, front-loaded with the action and resource. It does not waste words but also has no structure beyond that one line, leaving no room for conditionals.

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 3-parameter read tool with no output schema and no annotations, the description covers what comes back at a high level and the schema covers the parameters fully. However, it says nothing about the response shape, missing-record behavior, or the optional embedding payload, so it is adequate rather than complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the schema already documents id, include_cities, and include_embedding, making 3 the baseline. The description adds modest value by framing the payload as continent plus tags plus cities, which lines up with the include_cities default of true, confirming that cities are returned unless suppressed.

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?

States a specific verb (Retrieve) and resource (full profile of a sovereign country) plus the payload contents: continent, thematic statecraft tags, strategic cities. It clearly distinguishes a single-country fetch from list/sibling operations, though it never names an alternative tool.

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?

Usage is only implied: retrieve one country's profile by ID rather than listing or mutating. There is no explicit when-to-use versus when-not guidance, no mention of the create/update/delete siblings, and no guidance on when to flip include_cities or include_embedding.

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

Deploy Server