Skip to main content
Glama
Sign In
Houdini MCP

Houdini MCP

by beatreichenbach
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

create_lop_node

Creates a new LOP node under a specified parent path in Houdini using a chosen LOP type, with optional name and prim path.

Instructions

Create a new LOP node.

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": {
      "parent_path": "<parent_path>",
      "lop_type": "<lop_type>"
    },
    "name": "create_lop_node"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNo
lop_typeYes
prim_pathNo
parent_pathYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

D1.5/5.0
Behavior1/5

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

No annotations are supplied, so the description carries the full burden of behavioral disclosure, yet it says nothing. It does not state whether the node is created in the current scene, whether name is auto-generated when omitted, what happens with prim_path versus lop_type, what permissions are needed, or what the call returns.

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

Conciseness2/5

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

The single sentence is short but not concise in the useful sense: it is under-specified rather than trimmed. There is nothing front-loaded because there is nothing to front-load.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Against a mutation tool with 4 undocumented parameters, no annotations, and no output schema, a one-line restatement of the name is completely inadequate. Nothing is said about behavior, parameters, or results.

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

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% across all 4 parameters. The description adds no meaning to parent_path, lop_type, name, or prim_path, so an agent must guess at path formats and at how name and prim_path interact.

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

Purpose2/5

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

The description simply restates the tool name: "Create a new LOP node" repeats the verb and resource already encoded in create_lop_node. It does not differentiate LOP nodes from the many sibling creation tools (create_chop_node, create_cop_node, create_node, create_light will make hundreds of other nodes) or describe what a LOP node is or represents.

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 guidance on when to use this tool versus the numerous sibling tools, and no prerequisites or constraints are stated. The reader must infer that this is the right tool for LOP (Lighting/Stage) node creation purely from the name.

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