Skip to main content
Glama

list_cluster_snapshots

List frozen archetype cluster snapshots with pagination and target-type filters to inspect saved cluster states and optional groups.

Instructions

List frozen archetype cluster snapshots in Physicist.

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 (default: 20)
offsetNoPagination offset (default: 0)
target_typeNoFilter snapshots by entity target class
include_groupsNoInclude cluster groups in snapshot summary

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 disclosure burden. 'Frozen' hints the snapshots are immutable, but there is no statement of read-only semantics, default ordering, pagination behavior beyond the schema, or what a result entry looks like.

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 redundant clauses. It is efficient, though its brevity contributes to the gaps noted elsewhere.

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?

This is a low-complexity list tool with all-optional parameters and no output schema, so full return-value documentation is not required. Still, with zero annotations the description should say more about read-only safety and filtering behavior to be complete.

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 limit, offset, target_type, and include_groups all documented inline including defaults and enum values. The description adds no additional meaning about how these filters interact or what include_groups actually changes, 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 states a specific verb ('List') and resource ('frozen archetype cluster snapshots') scoped to the Physicist platform, which is enough to separate it from get_cluster_snapshot and create_cluster_snapshot. It stops short of naming a sibling explicitly, so it lands at 4 rather than 5.

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 guidance on when to call this versus get_cluster_snapshot (single item) or list_cluster_groups/list_cluster_reports. A reader must infer that 'List' means bulk enumeration with no lookup by id and no prerequisites.

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