Skip to main content
Glama

create_cluster_snapshot

Computes connected-components clustering for Species or Organism data and freezes the result into an immutable database snapshot for stable analysis.

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. 'Full Catalog Apex Predator Ecological Manifold (15)')
target_typeYesTarget entity class: Species or Organism
full_coverageNoForce 100% catalog coverage (zero singletons)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations supplied, the description carries the full disclosure burden, and it does add real signal: the operation runs a clustering computation and produces an immutable snapshot, so an agent knows the result cannot be edited afterward. It does not state whether the computation is synchronous or job-based, whether existing snapshots are affected, or what identifiers come back, which matters for a compute-plus-persist tool.

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 sentence, zero filler, and the key constraint (immediate freeze into an immutable snapshot) is front-loaded alongside the compute action. Nothing needs trimming.

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 schema is fully self-documenting and there is no output schema to explain, so the core invocation is covered. But a mutation-style tool that triggers a clustering computation and creates a durable artifact should at least indicate whether the call returns a snapshot reference or a job handle, and no annotations cover that gap.

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%, with all four parameters (level, title, target_type, full_coverage) documented in-schema including a helpful title example and the enum values. The description adds no parameter-level meaning beyond that, so the 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 uses a specific verb pair (compute, freeze) on a specific resource (cluster snapshot) and even names the underlying algorithm, connected-components clustering. That distinguishes it from a plain compute_clusters or create_cluster_report, though it never names those siblings 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: 'freeze it immediately into an immutable database snapshot' suggests you call this when you want a persistent, non-mutable result rather than a transient computation. There is no explicit when/when-not, no mention of prerequisites, and no routing to compute_clusters or create_cluster_report.

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