Statesman MCP Server

trigger_bulk_embeddings

Enqueue bulk embedding generation for all Country or City records, optionally limiting processing to records that lack embeddings.

Instructions

Enqueue bulk embedding generation for all Countries or Cities.

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": {
      "model_type": "<model_type>"
    },
    "name": "trigger_bulk_embeddings"
  }
}

Input Schema

Name	Required	Description	Default
`model_type`	Yes	Entity type to generate embeddings for: Country or City
`only_missing`	No	If true, only generate embeddings for records that are not yet embedded

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Nov 13, 2026

TDQS

B3.4/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 full behavioral burden. 'Enqueue' usefully discloses that this is an asynchronous job submission rather than a synchronous write, and 'all Countries or Cities' scopes the blast radius. However, it omits how the resulting job is tracked, whether re-runs are idempotent, and how the default only_missing=true affects scope.

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 fourteen-word sentence with the verb and scope front-loaded and no filler. Nothing could be trimmed without losing meaning.

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, asynchronous mutation with no annotations and no output schema, the definition is thin. An agent cannot learn from it how to confirm the enqueued job's progress, what the enqueue returns, or why it might want to override only_missing=false.

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 are already documented in the schema, including the enum values and the only_missing default. The description adds only the plural 'all' framing and otherwise restates the enum options, so 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 gives a specific verb plus resource: 'Enqueue bulk embedding generation' scoped to 'all Countries or Cities'. The word 'bulk' and 'all' implicitly distinguishes it from the single-record siblings generate_city_embedding and generate_country_embedding, though it never names them explicitly.

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?

Usage is implied rather than stated: 'bulk' and 'all' suggest this is the mass operation versus the per-record generate_*_embedding tools. There is no explicit when-to-use/when-not guidance, no mention of checking get_job_status after enqueueing, and no note about what happens if a run is already in flight.

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

Deploy Server