Skip to main content
Glama

get_attrib_values

Read a specific slice of one Houdini attribute as a flat, element-major array with pagination. Use it when you need indexed values from one attribute rather than a geometry sample.

Instructions

Read attribute values as a flat array with pagination.

For spot-checking a few values prefer sample_geometry — it returns a representative spread of points with all their attributes in one call. Use get_attrib_values when you need a specific slice of one attribute.

Values are element-major: for a float3 attribute every 3 consecutive values belong to one element. Check has_more and increment start to read subsequent pages.

Args: node_path: Node path. attrib_name: Attribute name. attrib_class: "point", "prim" (or "primitive"), "vertex", or "detail". start: First element index to return. count: Max elements per page (default 200).

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>",
      "attrib_name": "<attrib_name>"
    },
    "name": "get_attrib_values"
  }
}

Input Schema

NameRequiredDescriptionDefault
countNo
startNo
node_pathYes
attrib_nameYes
attrib_classNopoint

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

A4.4/5.0
Behavior4/5

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

With no annotations, the description carries the behavioral burden and does well: it identifies this as a read operation, explains the element-major flat-array layout, and describes pagination via has_more and start. It does not cover failure modes or node-cooking requirements, so it is strong but not exhaustive.

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?

The definition is front-loaded with purpose, then routes to the alternative, then explains element-major layout and pagination, followed by a compact Args list. The sentences are dense and every part supports correct invocation.

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 five-parameter tool with no output schema and no annotations, the description gives the key missing context: usage versus sample_geometry, flat-array output shape, has_more pagination, and valid attrib_class values. It remains slightly incomplete on node_path format, attrib_name examples, and error behavior.

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 0%, so the description must compensate. The Args section lists all parameters and usefully explains attrib_class values, start as an element index, and count as max elements per page, but node_path and attrib_name are nearly tautological and do not give path or naming examples.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource: read attribute values as a flat array with pagination. It also distinguishes the tool from sample_geometry by framing it as the choice for a specific slice of one attribute.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives explicit routing: use sample_geometry for spot-checking a few values, and use get_attrib_values when you need a specific slice of one attribute. It also explains how to page using has_more and start.

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