Skip to main content
Glama
Sign In
Statesman MCP Server

Statesman MCP Server

by leouofa
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

get_city

Retrieve a strategic city’s details by ID, including its structured themes, country, and continent, to support geopolitical and urban analysis.

Instructions

Retrieve details of a strategic city including its structured themes and associated country/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": {
      "id": "<id>"
    },
    "name": "get_city"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesCity ID
include_embeddingNoInclude raw 1024-dim vector embedding

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.2/5.0
Behavior3/5

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

No annotations are provided, so the description carries the burden; "Retrieve" signals a non-mutating read, which is useful. It also discloses the returned payload (themes, country/continent), but says nothing about behavior on a missing ID, permission needs, or the effect of the embedding flag.

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 front-loaded sentence with no filler; the resource and payload contents come before any qualifying detail. It is appropriately sized, though it could carry one more routing hint at little cost.

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 two-parameter read tool with full schema coverage and no output schema, the description reasonably summarizes the return payload. It falls short on failure behavior and on how the embedding flag changes the response, which matters since no annotations or output schema exist to cover those.

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 both parameters (id, include_embedding) are already documented at baseline. The description adds no format, range, or semantic detail beyond the schema, which is acceptable given 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?

States a specific verb ("Retrieve") and resource ("details of a strategic city") and names the payload contents (structured themes, associated country/continent). An agent can distinguish it from list_cities or create_city, though it doesn't explicitly name a sibling to route against.

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 when-to-use guidance, no exclusions, and no mention of alternatives such as list_cities for enumerating cities. The only usage signal is the implicit read-by-id pattern, which the agent must infer.

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