Statesman MCP Server

compute_clusters

Calculate live connected-component vector clusters for Countries or Cities across continents without changing the database, enabling counterpart discovery and comparative catalog analysis.

Instructions

Compute live connected-components vector clusters for Countries or Cities across continents without modifying the database.

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

Input Schema

Name	Required	Description	Default
`force`	No	Bypass Rails memory cache and recalculate adjacency graph
`level`	No	Similarity granularity level from 1 (strict twins, <= 0.16 cosine dist) to 15 (full coverage absorption, <= 0.30)
`target_type`	No	Target entity class to cluster: Country or City	Country
`full_coverage`	No	Forces 100% catalog assignment / zero singletons via nearest-cluster absorption

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Nov 13, 2026

TDQS

A3.5/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 and does disclose the key non-mutating behavior ('without modifying the database') plus that clusters are live. It omits return shape, computational cost, cache behavior tied to the force parameter, and whether results are deterministic or persisted.

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?

One front-loaded sentence with no filler. Every clause adds either scope or a behavioral constraint, and the read-only guarantee is placed clearly at the end.

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 definition covers core purpose and non-mutation, and the schema fully documents the four parameters. However, with no annotations and no output schema, it does not describe what a cluster result contains or how this tool relates to sibling cluster report/snapshot tools.

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 the schema already documents all four parameters thoroughly. The description mentions the Country/City target domain but adds no meaning for force, level, or full_coverage beyond what the schema provides.

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 ('Compute') and resource ('live connected-components vector clusters') and narrows the target to Countries or Cities. It is clear on its own, but it does not explicitly distinguish itself from sibling cluster-report or cluster-snapshot tools, so it falls short of a 5.

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 'live ... without modifying the database' implies transient, read-only use versus persisted snapshot/report tools, but no explicit when-to-use/when-not guidance or named alternative is given. The usage context is inferable rather than stated.

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

Deploy Server