Skip to main content
Glama
Sign In
Houdini MCP

Houdini MCP

by beatreichenbach
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

lock_parameter

Locks or unlocks a Houdini node parameter to prevent or restore editing during procedural workflow setup.

Instructions

Lock or unlock a parameter.

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>",
      "parm_name": "<parm_name>",
      "locked": "<locked>"
    },
    "name": "lock_parameter"
  }
}

Input Schema

NameRequiredDescriptionDefault
lockedYes
node_pathYes
parm_nameYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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 burden, yet it says nothing beyond the bare action. It does not explain what locking actually does (presumably preventing edits to the parameter value), whether the lock persists in the saved file, whether it requires the node to be unlocked by a parent, or what the result looks like on success or failure.

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 single sentence is front-loaded and free of padding, but the brevity comes at the cost of under-specification rather than being a tight, information-dense statement. Nothing is wasted, yet very little is delivered.

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?

This is a state-changing tool with no annotations, no output schema, and three fully undocumented parameters. An agent attempting to call it correctly needs to know what a node path looks like and what the lock flag does, and the definition provides none of that.

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% across three required parameters, so the description must compensate and does not. 'node_path', 'parm_name', and 'locked' are undocumented anywhere; the description only weakly hints that 'locked' means lock versus unlock and never clarifies path format or whether parm_name is a single parameter or a pattern.

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 gives a specific verb pair (lock/unlock) and a specific resource (a parameter), which is enough for an agent to understand the basic operation. It does not explicitly differentiate itself from siblings such as set_parameter or create_spare_parameter, so it stops short of 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 guidance about when to use this instead of set_parameter, revert_parameter, or create_spare_parameter, and no statement of prerequisites or side effects. The agent must infer usage entirely from the tool name and the boolean parameter.

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