Skip to main content
Glama

list_cluster_groups

Lists all archetype cluster groups for a specified frozen cluster snapshot, optionally including member subatomic particles or quantum states.

Instructions

List all archetype cluster groups belonging to a specific frozen 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": {
      "cluster_snapshot_id": "<cluster_snapshot_id>"
    },
    "name": "list_cluster_groups"
  }
}

Input Schema

NameRequiredDescriptionDefault
include_membersNoInclude member subatomic particles or quantum states
cluster_snapshot_idYesCluster Snapshot ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.3/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. 'List' implies a read, but nothing is said about pagination, result ordering, maximum result size, or required permissions on the snapshot; the only behavioral fact conveyed is the snapshot scoping.

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, front-loaded with the verb and resource, with the scoping condition as a trailing qualifier. No filler, redundancy, or restatement of the name.

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 two-parameter list tool with no output schema, the description covers what is returned at a high level. Without annotations it still omits the return shape (group fields), pagination behavior, and whether include_members materially changes the payload, which an agent would want before calling.

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 coverage is 100%, so both parameters are already documented, including include_members and its default. The description adds the notion that the snapshot must be 'frozen' for cluster_snapshot_id, but says nothing about the include_members toggle or what 'members' means in this tool's context.

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 names a specific verb and resource ('List all archetype cluster groups') plus a scoping constraint ('belonging to a specific frozen snapshot'), which separates it from the singular get_cluster_group and from list_particle_groups. It never names those siblings explicitly, so the differentiation is inferable rather than stated.

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 only implied: an agent can infer this is the tool for enumerating the groups inside one snapshot. There is no statement of when to prefer get_cluster_group or list_cluster_snapshots, and no prerequisites such as whether the snapshot must be frozen or already computed.

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