Skip to main content
Glama
Sign In
Statesman MCP Server

Statesman MCP Server

by leouofa
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

search

Searches sovereign countries and strategic cities across catalogs using semantic or keyword matching, so you can retrieve relevant geopolitical entities by query and filter by type.

Instructions

Unified cross-catalog semantic or keyword search across sovereign countries and strategic cities in the Statesman comparative geopolitics manifold.

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": {
      "q": "<q>"
    },
    "name": "search"
  }
}

Input Schema

NameRequiredDescriptionDefault
qYesSearch query text (e.g. 'maritime chokepoint gateway', 'sovereign wealth fund industrial policy')
modeNoSearch mode: semantic (pgvector cosine similarity), keyword (text matching), or autoauto
limitNoMaximum number of results to return (1-100)
target_typeNoFilter search results by entity type: all, country, or cityall

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.3/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; it discloses that this is a multi-catalog, dual-mode (semantic/keyword) retrieval operation, which is genuinely useful behavioral context. However, it says nothing about result ranking, whether mixed entity types come back interleaved, pagination behavior, or permissions, all of which an agent needs before invoking a search.

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 the searchable scope and modes stated first; the trailing domain branding is minor and the sentence contains no procedural padding or repetition.

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?

The tool is simple (4 params, fully described schema), but there are no annotations and no output schema, so the description should explain what results look like and how they are ordered. That gap leaves the definition only minimally viable for an agent deciding whether to call it.

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 coverage is 100%, so the query text, mode enum, limit range, and target_type filter are already fully documented in the schema. The description only echoes 'semantic or keyword' and the country/city scope, adding no syntax, ranking, or filtering nuance beyond structured data, so the baseline 3 applies.

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 clear verb and resource: a search over countries and cities, with 'semantic or keyword' naming the retrieval mechanism. It is specific enough to distinguish a search operation from CRUD siblings, but it does not name or contrast itself with related query tools like find_counterparts 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?

There is no explicit when-to-use or when-not-to-use guidance, and no alternatives are named. 'Unified cross-catalog' implies it spans entity types, but an agent must infer when search beats list_cities, get_country, or find_counterparts, and when to pick semantic vs keyword mode.

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