Skip to main content
Glama
Sign In
Statesman MCP Server

Statesman MCP Server

by leouofa
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

list_countries

Lists and filters sovereign countries by continent, theme, search query, and embedding status, optionally including strategic cities and vector data for geopolitical analysis.

Instructions

List and filter sovereign countries with statecraft themes, city counts, and vector embedding status.

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

Input Schema

NameRequiredDescriptionDefault
qNoSearch country name or description substring
limitNoPagination limit (default: 50)
themeNoFilter countries containing thematic tag (e.g. 'maritime', 'federal')
offsetNoPagination offset (default: 0)
embeddedNoFilter by whether vector embedding has been generated
continentNoFilter by continent name substring (e.g. 'Europe')
continent_idNoFilter by continent ID
include_citiesNoInclude associated strategic cities
include_embeddingNoInclude raw 1024-float vector array

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

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 behavioral-disclosure burden. It implies a read-only listing operation, but it does not state whether results are paginated, how they are ordered, whether the operation has side effects, or what the response looks like. Some filtering dimensions are mentioned, but key behavioral traits remain undisclosed.

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?

The description is a single front-loaded sentence with no filler, and it places the main action first. It is appropriately concise, though the phrase 'with statecraft themes, city counts, and vector embedding status' is slightly compressed and could be clearer about what is filtered versus returned.

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?

This is a nine-parameter listing tool with no annotations and no output schema, so the description needs to carry more context than a single sentence provides. It does not explain pagination behavior, return shape, how include_cities or include_embedding affect results, or how continent and continent_id relate. The schema covers parameter semantics, but the description is incomplete for the tool's complexity.

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 nine parameters already have documented meaning in the schema. The description adds only high-level references to filtering by themes, city counts, and embedding status, without adding syntax, defaults, or relationships beyond what the schema provides. The baseline of 3 is appropriate.

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 states a specific verb ('List and filter') and resource ('sovereign countries'), and it names relevant data dimensions such as statecraft themes, city counts, and vector embedding status. It clearly identifies the tool's purpose, though it does not explicitly distinguish it from sibling list tools like list_continents or list_cities.

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 states what the tool does; it gives no explicit guidance on when to use this tool versus alternatives, nor does it mention prerequisites or exclusion scenarios. Usage is implied by 'List and filter sovereign countries,' but there is no actionable when-to-use instruction.

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

Deploy Server

Other Tools