Skip to main content
Glama
Sign In
Houdini MCP

Houdini MCP

by beatreichenbach
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

list_hda_versions

Retrieves all installed definitions for a specified HDA type, helping you inspect available versions on a node path before choosing or managing assets.

Instructions

List installed definitions of an HDA type.

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

Input Schema

NameRequiredDescriptionDefault
node_pathYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations, “List” is the only indication that the operation is nonmutating. The description does not clarify definition sources, whether current and historical versions are included, result ordering, or behavior for missing nodes and empty results.

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 single sentence is front-loaded and contains no unnecessary wording. Its brevity is efficient, though it leaves important terminology and input relationships unstated.

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?

The basic operation is understandable, but there is no supporting annotation, parameter documentation, or output schema to fill the gaps. Reliable invocation still requires guessing how node_path selects the HDA type and what constitutes an installed definition or version.

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?

The sole parameter, node_path, has no schema description and is never mentioned in the description. “Of an HDA type” indirectly suggests that the path identifies a node whose type should be inspected, but it does not confirm that relationship or specify the accepted path form.

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 uses a clear verb and resource: listing installed definitions for a specific HDA type. However, it does not explain how “definitions” relates to the “versions” in the tool name or explicitly distinguish the tool from siblings such as list_installed_hdas or get_hda_info.

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 per-type scope implies that this tool is used after identifying an HDA type whose installed definitions are needed. It provides no explicit guidance about when to choose it over other HDA inspection or listing tools, nor any prerequisites for invocation.

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