Skip to main content
Glama
Sign In
Statesman MCP Server

Statesman MCP Server

by leouofa
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

populate_cities_bulk

Run bulk LLM city discovery across all countries or scope it to a single country to populate urban catalogs.

Instructions

Trigger bulk LLM city discovery across all countries or a single country.

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

Input Schema

NameRequiredDescriptionDefault
syncNoIf true, wait synchronously for completion
country_idNoOptional country ID to scope discovery

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.2/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full burden. It says "Trigger" but never discloses that this is a long-running LLM job (there is a get_job_status sibling), whether it overwrites or duplicates existing city records, whether it is safe to re-run, or what the cost/rate implications are. Only the sync-vs-async choice is hinted at, via the schema rather than the description.

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 zero filler; the verb, resource, and scope arrive immediately. Nothing redundant is present.

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 bulk LLM trigger with no annotations and no output schema, the definition is too thin: it does not say what is returned (a job handle?), how completion is observed, or what happens to existing data. An agent can guess the intent but not the operational consequences of calling 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 schema already documents both country_id and sync. The description adds one useful nuance: omitting country_id means all countries. That is a modest gain over the schema, which merely labels it "optional".

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 concrete verb ("Trigger") and resource ("bulk LLM city discovery") plus the scope ("all countries or a single country"), which lets an agent distinguish it from narrower siblings like populate_country_cities. It stops short of naming the sibling it replaces, so differentiation is inferred rather than explicit.

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?

The phrase "across all countries or a single country" implies the two usage modes, but there is no statement of when to prefer this over populate_country_cities, populate_cities_batch, or upsert_cities_batch, and no prerequisites or exclusions. Usage is only implied.

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