Skip to main content
Glama

list_cluster_snapshots

Lists frozen archetype cluster snapshots in Biologist, with pagination and optional filtering by Species or Organism target type.

Instructions

List frozen archetype cluster snapshots in Biologist.

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: Species or Organism

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 behavioral burden, yet it only implies read-only behavior through the word "List." It says nothing about pagination defaults/caps, whether results are scoped to a workspace or project, what a "frozen" snapshot means operationally, or what happens when the filter matches nothing.

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 filler, which is efficient. The brevity borders on under-specification rather than genuine concision, but nothing in it is wasted or buried.

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 three-parameter read-only list tool with no output schema, the essential facts (resource identity, filter, pagination) are covered by name and schema. Still missing is anything an agent would want before calling: read-only confirmation, default page size behavior, and the relationship to the sibling snapshot and group 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%, and the schema already documents `limit` (1-100, default 20), `offset`, and the `target_type` enum with its Species/Organism values. The description adds nothing beyond the schema, so the baseline 3 applies; the phrase "frozen archetype" hints at entity semantics but not at parameter behavior.

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 gives a specific verb-plus-resource ("List ... cluster snapshots") and adds the qualifier "frozen archetype," which distinguishes it from the create/delete snapshot siblings by intent. It does not, however, differentiate itself from `list_cluster_groups`, `list_cluster_reports`, or `get_cluster_snapshot`, leaving the agent to infer the boundary from names alone.

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 guidance, no mention of when to prefer `get_cluster_snapshot` (single item) or `list_cluster_groups` (parent resource), and no stated preconditions. The agent must derive invocation context entirely from the tool name.

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