Skip to main content
Glama

create_spare_parameters

Batch-create or update multiple spare parameters on a Houdini node in one call, optionally grouping them in a named folder tab while preserving existing values and keyframes.

Instructions

Batch-create multiple spare parameters in one call, optionally in a folder tab.

A name that already exists as a spare parameter is updated in place (label, default, range); its current value and keyframes are kept. A type change on an existing parameter is refused.

Args: node_path: Node path. parameters: List of parameter specs. Each dict has keys: parm_name (str), parm_type (str: "float"/"int"/"string"/"toggle"/"menu"/ "vector"/"color"/"ramp_float"/"ramp_color", as in create_spare_parameter), label (str), default_value (optional; a ramp's keys), min_val (optional), max_val (optional), menu_items (a menu's items: strings or [value, label] pairs, as in create_spare_parameter; default_value then picks one). folder_name: If provided, wraps all parameters in a named folder tab. folder_type: Folder style: "Tabs", "Collapsible", or "Simple".

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

Input Schema

NameRequiredDescriptionDefault
node_pathYes
parametersYes
folder_nameNo
folder_typeNoTabs

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.24.1
    • addedInput schema / additionalProperties
      Added value: +false
  2. First observedv0.1.0

TDQS

A4.5/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full burden and delivers meaningful behavior: an existing name is upserted in place with label/default/range updated while its value and keyframes are preserved, and a type change is refused. It omits what happens if folder_name collides with an existing folder and what the response contains (created vs updated), leaving a real gap.

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 key behavior is front-loaded before the Args block, and the length is defensible given the zero schema coverage and complex nested payload. Line breaks fall mid-sentence (e.g. between 'menu'/'vector' and after 'label (str)'), slightly hurting scannability, but no sentence is filler.

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

Completeness5/5

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

For a batch mutation tool with a nested parameter array, no annotations, and no output schema, this is close to complete: mutation semantics, upsert behavior, refusal condition, and the entire payload shape are covered. Only the return value and folder-name collision case remain unaddressed, which is a minor residual against the complexity handled.

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

Parameters5/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 entirely, and it does: every argument is documented, plus the full nested spec of each parameter dict (parm_name, parm_type with its nine allowed values, label, default_value, min_val, max_val, menu_items with both string and [value, label] forms). The folder_type enum values are also enumerated in prose.

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 opens with a specific verb and scope: 'Batch-create multiple spare parameters in one call, optionally in a folder tab.' This clearly distinguishes it from the singular sibling create_spare_parameter, which is also explicitly cited as the reference for per-parameter semantics.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The batching rationale ('multiple ... in one call') makes the choice against create_spare_parameter largely self-evident, and the folder_name arg is framed conditionally ('If provided'). There is no explicit 'use X instead when...' routing statement or prerequisite/permission guidance, so it stops short of a 5.

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