Skip to main content
Glama

get_group_members

Retrieve paginated element indices from a Houdini geometry group by node path, group name, and type; use start/count and has_more to read subsequent pages.

Instructions

Get element indices in a geometry group, with pagination.

Check has_more and increment start to read subsequent pages.

Args: node_path: Node path. group_name: Group name. group_type: "point", "prim" (or "primitive"), or "edge". start: First element index to return. count: Max elements per page (default 5 000).

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": {
      "node_path": "<node_path>",
      "group_name": "<group_name>"
    },
    "name": "get_group_members"
  }
}

Input Schema

NameRequiredDescriptionDefault
countNo
startNo
node_pathYes
group_nameYes
group_typeNopoint

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.24.1
    • addedInput schema / additionalProperties
      Added value: +false
  2. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose the pagination model and that results include a has_more flag. It says nothing about read-only safety, error behavior for a missing node/group, or whether indices are sorted, leaving meaningful behavioral gaps for a 5-parameter tool.

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?

The behavior statement is front-loaded in the first two sentences and the Args block is compact. A small amount of space is wasted on tautological parameter glosses like 'Node path: Node path.' and 'Group name: Group 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?

Given no annotations and no output schema, the description covers the essentials of what is returned (element indices) and how to page through it. It is still missing the expected form of node_path, behavior on non-existent groups, and confirmation that this is a non-mutating read, which matters for an unannotated tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the Args block is doing real work: it supplies the accepted group_type values ('point', 'prim'/'primitive', 'edge') that the schema does not constrain with an enum, and explains start/count paging semantics. The node_path and group_name entries are tautological restatements, which keeps it from a 5.

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 first sentence names a specific verb (get) and resource (element indices within a geometry group) plus its pagination scope, which is far more informative than the bare tool name. It stops short of explicitly distinguishing itself from the sibling get_groups (which enumerates groups rather than their members), so it is clear but not fully disambiguated.

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 pagination instruction ('Check has_more and increment start to read subsequent pages') is genuine when-to-use guidance for iterating results. However, there is no guidance on when to call this versus get_groups or get_points/get_prims, nor any prerequisites such as requiring a valid node path or existing group.

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

Deploy Server

Other Tools