Skip to main content
Glama
Sign In
Houdini MCP

Houdini MCP

by beatreichenbach
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

find_nodes

Search Houdini scenes for nodes by name pattern, type, or context to locate specific nodes and target them for workflow automation.

Instructions

Search for nodes by name pattern, type, or context.

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": "find_nodes"
  }
}

Input Schema

NameRequiredDescriptionDefault
insideNo/
contextNo
patternNo
node_typeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.7/5.0
Behavior2/5

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

With no annotations, the description must carry the behavioral disclosure burden. "Search" implies a read-only lookup, but the description does not state scope behavior, result limits, pagination, permissions, or what kind of node references are returned.

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 description is a single front-loaded sentence with no wasted wording. However, it is arguably too terse for a four-parameter search tool with no schema descriptions, which limits how appropriately sized it feels.

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?

Given four parameters, zero schema description coverage, and no annotations or output schema, the definition is incomplete. An agent would still not know how to use "inside," what pattern syntax is accepted, what node types are valid, or what the results look like.

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 needs to explain all four parameters. It loosely maps three of them (pattern, node_type, context) to search dimensions but never explains the important "inside" scope parameter, pattern syntax, node_type values, or context semantics.

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 specific verb and resource: "Search for nodes." It also names three search dimensions (name pattern, type, context), so the core purpose is clear. It does not distinguish this generic search from specialized siblings such as find_error_nodes or find_expensive_nodes, which keeps it from a 5.

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 explicit guidance on when to use this tool versus the specialized find_* alternatives or listing tools. The phrase "Search for nodes by..." implies a lookup use case, but no conditions, exclusions, or alternatives are stated.

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