Skip to main content
Glama

get_cluster_snapshot

Retrieve a frozen cluster snapshot to review member groups, species or organisms, and generated synthesis reports for ecological and taxonomic analysis.

Instructions

Retrieve details of a frozen cluster snapshot including member groups and generated synthesis reports.

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": {
      "id": "<id>"
    },
    "name": "get_cluster_snapshot"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesCluster Snapshot ID
include_groupsNoInclude discovered archetype cluster groups
include_membersNoInclude species or organisms belonging to each group
include_reportsNoInclude generated scholarly reports

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 supplied, so the description carries the full burden. 'Frozen' hints at immutability and the operation is implicitly a read, but nothing states that it is non-mutating, what permissions are needed, or what happens for an unknown or non-frozen ID.

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?

It is a single front-loaded sentence with no filler. The only weakness is that it spends its words on payload contents that the schema already enumerates.

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?

Simple get-by-id tool with fully documented parameters, but no output schema, so the description's brief list of returned sections is doing real work. It is adequate but thin given the absence of annotations and return-value documentation.

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 every parameter documented including defaults. The description's mention of member groups and reports loosely echoes the include_* flags but adds no syntax, format, or interaction detail beyond the schema, 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 has a specific verb ('Retrieve') and resource ('frozen cluster snapshot') plus a short enumeration of the payload (member groups, synthesis reports). It is clear enough to distinguish from list_cluster_snapshots, but it never names that sibling or otherwise makes the distinction explicit.

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 when-to-use or when-not guidance and no named alternative. The agent must infer from the required 'id' parameter that this is a fetch-by-identifier operation and that listing must come first.

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