Statesman MCP Server

create_country

Create a new sovereign country record tied to a continent, with thematic tags and governance details for geopolitical cataloging.

Instructions

Create a new sovereign country record associated with a continent.

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": {
      "continent_id": "<continent_id>",
      "name": "<name>"
    },
    "name": "create_country"
  }
}

Input Schema

Name	Required	Description
`name`	Yes	Name of the sovereign country (e.g. 'Japan', 'France')
`themes`	No	Thematic statecraft tags (e.g. ['island', 'tech', 'maritime trade'])
`description`	No	Scholarly description of governance, strategic geography, and political economy
`continent_id`	Yes	Continent ID

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Nov 13, 2026

TDQS

C2.9/5.0

Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It implies a mutation but says nothing about permission requirements, duplicate-name handling, failure modes when continent_id is invalid, or whether any related records are created; 'associated with a continent' hints at a foreign-key requirement but does not explain its enforcement.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence with no filler. It states the action and the key relationship immediately, though the brevity is also the source of the gaps elsewhere.

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 mutation tool with zero annotation coverage and no output schema, the definition is too thin: it never states what is returned on success, whether the name must be unique, or what happens if continent_id does not exist. The fully described schema compensates for parameter questions but not for creation semantics.

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

Parameters3/5

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

Schema description coverage is 100%, so all four parameters (name, themes, description, continent_id) are already documented with examples in the schema. The description only reinforces that continent_id links the record to a continent, adding little beyond the schema's own wording, which fits the baseline 3 for full 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 gives a specific verb ('Create') and resource ('a new sovereign country record') and adds the continent association, which maps to the required continent_id. It is not explicitly contrasted with sibling tools like create_continent, update_country, or create_city, but the resource is unambiguous.

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 statement of when to use this tool versus alternatives such as update_country (modifying an existing country) or create_continent. The agent must infer that this is for net-new country creation from the word 'Create' alone, with no exclusions or prerequisites given.

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

Deploy Server