Skip to main content
Glama

get_cluster_group

Retrieve details for a specific archetype cluster group, including its member subatomic particles or quantum states, to inspect group composition and relationships.

Instructions

Retrieve details of a specific archetype cluster group with all member subatomic particles or quantum states.

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 subatomic particles or quantum states

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.4/5.0
Behavior3/5

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

No annotations are supplied, so the description must carry the behavioral burden. It implies a safe read ('Retrieve', 'details') and discloses that member particles/states are returned, but says nothing about error behavior for invalid IDs, permissions, or response size for large clusters.

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 the verb first and no filler. It is appropriately sized for a simple lookup, though one clause clarifying members versus details would still earn its place.

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?

With no output schema, the description must convey return shape, and it only says 'details' plus members without enumerating fields. For a two-parameter read tool this is largely adequate, but an agent cannot predict the payload structure from it.

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 both 'id' and 'include_members' are already documented in the schema, establishing a baseline of 3. The description adds the useful detail that members are 'subatomic particles or quantum states', but never explains the include_members toggle, so it adds little 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 details') and resource ('a specific archetype cluster group'), and adds the scope of what comes back ('all member subatomic particles or quantum states'). This lets an agent distinguish it from listing tools like list_cluster_groups, though it does not name any sibling explicitly.

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?

The word 'specific' combined with a required ID implies the tool is for fetching one known group rather than enumerating groups, which is usable implied guidance. However, there is no explicit when-to-use statement, no mention of list_cluster_groups as the alternative for discovery, and no prerequisites such as what happens with an unknown ID.

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