Skip to main content
Glama
ChengZiiii

opera-houdini-mcp

by ChengZiiii

create_spare_parameter

Create a single spare parameter on a Houdini node, choosing its data type (float, int, string, toggle, or menu) and setting optional attributes like label, default, min/max, and menu items.

Instructions

单项 spare 参数创建(add-node-parameter-vex-tools,MUTATING)。

通过 ``parmTemplateGroup()`` 复制 + 一次性
``setParmTemplateGroup()`` 提交。``data_type`` 接受 ``float / int /
string / toggle / menu``。``folder`` 可选。响应过
``apply_response_cap``。

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
ctxYes
nameYes
pathYes
labelNo
folderNo
defaultNo
data_typeYes
max_valueNo
min_valueNo
menu_itemsNo
menu_labelsNo
num_componentsNo
Behavior4/5

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

The description explicitly marks the tool as MUTATING and discloses the implementation mechanism (parmTemplateGroup() copy + setParmTemplateGroup() commit). This gives the agent awareness of the mutation without relying on annotations. It does not detail side effects or reversibility, but the core mutating behavior is clearly stated.

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 compact, consisting of three short sentences that front-load the purpose. However, it includes low-level implementation details (e.g., 'parmTemplateGroup() copy') that might not be necessary for an agent to invoke it correctly, slightly reducing clarity.

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 the tool's complexity (12 parameters, no output schema, no annotations), the description is incomplete. It does not explain most parameters, provide examples, or describe return values/errors. An agent would likely struggle to use it correctly without additional information.

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. It adds meaning for data_type (lists accepted values) and folder (optional), but the other 10 parameters (ctx, path, name, label, default, etc.) remain undocumented. This is insufficient for a 12-parameter tool.

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

Purpose5/5

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

The description clearly states '单项 spare 参数创建' (single spare parameter creation), which identifies the action and resource. It distinguishes itself from sibling tool create_spare_parameters by emphasizing the singular nature ('单项'), providing clear scope.

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 description implies usage for a single parameter via the '单项' qualifier and the singular name, but does not explicitly say when to use this over create_spare_parameters or other parameter tools. No direct alternatives or exclusion criteria are mentioned.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/ChengZiiii/opera-houdini-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server