Skip to main content
Glama

create_cluster_snapshot

Computes connected-components clustering and freezes the result into an immutable database snapshot to preserve reproducible cluster states.

Instructions

Compute connected-components clustering and freeze it immediately into an immutable database snapshot.

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": {
      "target_type": "<target_type>",
      "level": "<level>",
      "title": "<title>"
    },
    "name": "create_cluster_snapshot"
  }
}

Input Schema

NameRequiredDescriptionDefault
levelYesSimilarity granularity level (1 to 15)
titleYesDescriptive title for the frozen snapshot (e.g. 'Level 5 Standard Model Multiplet Manifold')
target_typeYesTarget entity class: SubatomicParticle or QuantumState
full_coverageNoForce 100% catalog coverage (zero singletons)

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?

With no annotations present, the description does carry useful behavioral weight: it declares a persistent write and states the resulting snapshot is immutable and created immediately. It omits other relevant traits such as how expensive the clustering may be, whether repeated calls produce duplicate snapshots, permission requirements, or what is returned (no output schema exists).

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 a clear action and outcome and no filler. It is compact to the point of omitting any usage or return context, but nothing present is redundant.

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 four-parameter mutation tool with no annotations and no output schema, the description covers the core action and the immutability of the result but not the return value (e.g., snapshot identifier) or any precondition. The individual parameters are fully documented by the schema, so the main remaining gap is around outcomes rather than inputs.

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% across all four parameters, including the level range, target_type enum, title, and full_coverage default, so the schema already does the work. The description adds no extra meaning about how level or full_coverage affect the clustering or the frozen result, which is the baseline-3 case.

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?

Contains a specific verb phrase ('Compute connected-components clustering') plus the resource it produces ('immutable database snapshot'), so the agent knows this both computes and persists. It does not explicitly distinguish itself from compute_clusters (compute-only?) or create_cluster_report, leaving that differentiation to inference from names.

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?

There is no explicit when-to-use, when-not-to-use, or named alternative. The only guidance is implicit: the word 'freeze' suggests using this when a durable clustering result is needed rather than a transient computation, but the agent must guess the boundary against compute_clusters and the report/group tools.

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