Skip to main content
Glama

get_attribute_info

Retrieve metadata for a geometry attribute on a Houdini node using its node path, attribute name, and optional attribute class (point, primitive, vertex, or detail).

Instructions

Get metadata for a geometry attribute.

Args: node_path: Node path. attrib_name: Attribute name. attrib_class: "point", "prim" (or "primitive"), "vertex", or "detail".

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

Input Schema

NameRequiredDescriptionDefault
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

C2.8/5.0
Behavior2/5

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

With no annotations at all, the description carries the full behavioral burden. 'Get' implies a read, but nothing states whether the node must be cooked, what happens if the attribute doesn't exist, or what metadata fields (type, size, tuple size, qualifier) come back. For a tool with zero annotation coverage this is a substantial gap.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The lead sentence is front-loaded and the attrib_class line earns its place. The other two Args lines merely echo the parameter titles and add no information, so part of the text is boilerplate rather than value.

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?

There is no output schema and no annotations, so the description is the only source of truth. It never says what 'metadata' contains or how errors are surfaced, which is insufficient for a tool whose whole purpose is returning structured descriptive data.

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. It does add real meaning for attrib_class by enumerating 'point', 'prim'/'primitive', 'vertex', and 'detail' — information the schema lacks entirely. But node_path and attrib_name are restated tautologically ('Node path.', 'Attribute name.'), and the default of 'point' is not mentioned.

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 states a specific verb and resource: 'Get metadata for a geometry attribute.' An agent knows this returns descriptive info rather than values. However, it never distinguishes itself from close siblings such as get_attrib_values, get_attrib_stats, or get_geometry_info, leaving the agent to guess which one to pick.

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 when-to-use guidance, no prerequisites (e.g. node must be cooked or be a SOP), and no named alternatives. The only implied usage is the contrast between 'metadata' and 'values,' which the agent has to infer from sibling names alone.

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