Skip to main content
Glama
Sign In
Statesman MCP Server

Statesman MCP Server

by leouofa
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

list_cluster_snapshots

List frozen archetype cluster snapshots with pagination and optional filters by target type (Country or City), including cluster groups, to review saved comparative clusters.

Instructions

List frozen archetype cluster snapshots.

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

Input Schema

NameRequiredDescriptionDefault
limitNoPagination limit
offsetNoPagination offset
target_typeNoFilter by target entity type: Country or City
include_groupsNoInclude cluster groups for each snapshot

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden. The word 'frozen' hints that snapshots are immutable, but it does not disclose pagination behavior, whether results are sorted or truncated, or what a response contains. For a list tool with zero annotation coverage this is a meaningful gap.

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 wasted wording. It is efficient, though its brevity leaves behavioral and selection context unaddressed.

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?

The tool has four parameters, pagination controls, and an enum filter, yet the description explains none of them and omits return-shape expectations. Without annotations or an output schema, the brief description is not sufficient to guide correct invocation beyond the schema.

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%, and all four parameters—limit, offset, target_type, and include_groups—are documented in the schema itself. The description adds no additional meaning or syntax guidance beyond what the schema provides, so the baseline of 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?

States a specific verb (list) and resource (frozen archetype cluster snapshots), making the operation recognizable. It does not distinguish itself from related siblings such as get_cluster_snapshot or list_cluster_groups, but the core purpose is unambiguous.

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?

Gives no indication of when to use this tool versus get_cluster_snapshot, list_cluster_groups, or list_cluster_reports. There is no when/when-not guidance or mention of prerequisites, so an agent must infer selection from the name alone.

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