Skip to main content
Glama

get_cluster_group

Retrieve details of an archetype cluster group, including its member species or organisms, by ID to inspect group composition and taxonomy.

Instructions

Retrieve details of a specific archetype cluster group with all member species or organisms.

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_group"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesCluster Group ID
include_membersNoInclude member species or organisms

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.5/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries the full disclosure burden. It implies a read-only retrieval and usefully discloses that the response includes member species or organisms, but says nothing about permissions, whether missing IDs error, or response size/volume despite the member expansion.

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 efficient sentence that front-loads the verb and resource with zero filler. Slightly more compact than needed, since the brevity is what leaves sibling differentiation unaddressed.

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

Completeness4/5

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

For a simple two-parameter read with full schema coverage and no output schema, the description conveys the key output characteristic (members included) and the lookup semantics. Only the routing versus list_cluster_groups and the include_members toggle remain unstated.

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 (id, include_members) are already documented in the schema, making 3 the baseline. The phrase 'with all member species or organisms' loosely corresponds to include_members, but the description never notes that member inclusion is toggleable, adding no real meaning beyond the schema.

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?

States a specific verb ('Retrieve') and resource ('details of a specific archetype cluster group'), plus scope ('with all member species or organisms'). It is clear what the tool returns, but it never distinguishes itself from siblings such as list_cluster_groups, so an agent must infer the singular-vs-list split from the ID requirement.

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: 'specific ... group' signals a single-record lookup keyed by an ID, which implicitly contrasts with the listing tool. There is no explicit when-to-use or when-not guidance, and no mention of the sibling list_cluster_groups as the alternative for enumerating groups.

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