Skip to main content
Glama

list_cluster_groups

Retrieve archetype cluster groups from a specific frozen snapshot to inspect clustered taxonomic data, with pagination controls and optional member species inclusion.

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
limitNoPagination limit
offsetNoPagination offset
include_membersNoInclude member species or organisms
cluster_snapshot_idYesCluster Snapshot ID

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?

With no annotations, the description carries the whole burden. 'List all' implies a complete, side-effect-free enumeration, yet the schema defaults limit=50 and include_members=true, so the 'all' claim is misleading about default result scope and the description says nothing about pagination, whether an unknown snapshot yields an error or an empty list, or what members are.

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?

One front-loaded sentence with no filler or redundancy; the scope qualifier appears immediately after the verb and resource. It is efficient, though the brevity is achieved by omitting rather than compressing useful detail.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a four-parameter tool with no annotations and no output schema, the description leaves out pagination behavior, the default inclusion of members, and the shape of what is returned. The agent would need to open the schema and guess at runtime semantics before calling it confidently.

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%, so limit, offset, include_members, and cluster_snapshot_id are already documented in the schema. The description only adds the qualifier 'frozen' to the snapshot concept and adds no syntax, format, or interaction details (e.g. how include_members changes the payload), so the baseline of 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 names a specific verb and resource ('List all archetype cluster groups') and scopes it to 'a specific frozen snapshot', which separates it from the singular get_cluster_group and from list_cluster_snapshots. It stops short of explicitly naming the sibling it is not, so it is clear but not fully differentiated.

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 explicit when-to-use statement and no exclusion of alternatives; the agent must infer from 'belonging to a specific frozen snapshot' that this is the read path for groups inside one snapshot rather than a single-group lookup. Listing or fetching one group via get_cluster_group is never mentioned.

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