Skip to main content
Glama

get_hda_info

Retrieves detailed information about a Houdini Digital Asset (HDA) definition using a node path, HDA file, or type name.

Instructions

Get detailed information about an HDA definition.

Args: ctx: MCP context. node_path: Node path. hda_file: HDA file path; variables ($JOB) are expanded. type_name: HDA type name.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_hda_info"
  }
}

Input Schema

NameRequiredDescriptionDefault
hda_fileNo
node_pathNo
type_nameNo

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.6/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden. It implies a read via "Get" and discloses that $JOB variables in hda_file are expanded, but says nothing about what "detailed information" contains, whether the selectors are mutually exclusive, or what happens if multiple/zero are passed.

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 one-line purpose sentence is front-loaded and efficient. However, the Args block spends most of its length restating schema titles verbatim, which adds bulk without information.

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?

For a tool with three undocumented optional selectors and no output schema, the definition is too thin: it doesn't say what fields the returned HDA info includes, nor which selector is preferred. The only compensating detail is the variable-expansion note.

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

Parameters2/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, and it largely does not: "node_path: Node path" and "type_name: HDA type name" merely restate the parameter names. The one genuine addition is that hda_file expands variables such as $JOB, but there is no explanation of how the three selectors relate or which combination is valid.

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 and resource: "Get detailed information about an HDA definition." An agent knows this returns HDA metadata, but the description never distinguishes it from siblings like get_hda_sections or get_hda_section_content, which sound closely related.

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?

Provides no when-to-use guidance, no prerequisites, and no mention of alternatives. With three optional selector parameters, the agent is given no help deciding when this tool is the right choice over the sibling HDA inspection tools.

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