Skip to main content
Glama

set_parameters

Set multiple node parameters in one batch, including expressions and ramps, with optional callback execution and expression override for locked or linked parameters.

Instructions

Batch-set multiple parameters on a node, in the order given.

Expressions go in the same call: {"tx": {"expr": "ch('../size')"}} sets an expression, so no set_expression per parameter is needed.

Inside a DOP network a write does not reset frames already simulated: simulation_cache names the network to pass to reset_simulation.

Parameters that held an expression and therefore ignored the literal are listed in expressions_kept, with a top-level warning: a batch whose errors is empty can still contain a write that did not take. Values that landed on ANOTHER node, because the parameter is a bare ch() reference Houdini writes through, are in written_through. Each entry in set carries the same keys as set_parameter's reply. Pass override_expression=True to clear those expressions and links instead.

Locked parameters are in errors with locked: true and listed in locked_parms; the error names the menu whose callback sets the lock. With run_callbacks=True each parameter's callback runs after its write, so {"res_mode": "manual", "resolutiony": 1080} unlocks and then writes; a callback that raised is listed in callbacks_not_run.

Args: node_path: Node path. params: Mapping of parameter names to values, written in this order. A value written {"expr": "...", "language": "hscript" | "python"} is set as an expression, as in build_network, also as one component of a list ("t": [{"expr": "$F"}, 0, 0]). A ramp takes the whole ramp at once: {"keys": [0, 1], "values": [[1, 0, 0], [0, 0, 1]], "basis": "linear"} (one basis or one per key; a float ramp takes numbers), the shape get_parameter reads it in. A ramp's new_value is what it holds once the whole call is through, so a key added by count and then set reads as set. override_expression: Remove expressions standing in the way. run_callbacks: Run each parameter's callback script after its write, as the UI does.

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>",
      "params": "<params>"
    },
    "name": "set_parameters"
  }
}

Input Schema

NameRequiredDescriptionDefault
paramsYes
node_pathYes
run_callbacksNo
override_expressionNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv2.24.1
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / run_callbacks
      Added value: +{
      +  "default": false,
      +  "title": "Run Callbacks",
      +  "type": "boolean"
      +}
  2. Changed1 schema field changedv2.21.0
    • addedInput schema / properties / override_expression
      Added value: +{
      +  "default": false,
      +  "title": "Override Expression",
      +  "type": "boolean"
      +}
  3. First observedv0.1.0

TDQS

A4.6/5.0
Behavior5/5

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

With no annotations, the description carries the full burden and does so: it warns that a batch with empty errors can still contain a write that did not take, explains expressions_kept/set/written_through/errors/locked_parms/callbacks_not_run, and notes that writes inside a DOP network do not reset already-simulated frames unless simulation_cache is passed to reset_simulation. These are non-obvious failure modes an agent could not infer from the schema.

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?

It is front-loaded with the core action and the most surprising caveats, and the Args block is clearly separated. It is dense and the ramp paragraph runs long, but nearly every sentence carries semantic load rather than restating the schema.

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

Completeness4/5

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

There is no output schema, and the description does document the reply shape (set entries match set_parameter's reply, plus expressions_kept, written_through, locked_parms, callbacks_not_run, warning), which is what completeness requires here. Given four parameters, nested values, and no annotations, the coverage is strong, though ordering interactions between override_expression and run_callbacks could be spelled out more explicitly.

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 coverage is 0%, so the description must compensate and it does: it defines params as an ordered name-to-value mapping and specifies the nested value forms (expr+language objects, list components, whole-ramp dicts with keys/values/basis, the new_value semantics). override_expression and run_callbacks are explained with their write-ordering behavior, not just their names.

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 first sentence states a specific verb and resource (batch-set parameters on a node) plus a distinguishing property (order is preserved). It also names set_expression as the thing it replaces per-parameter, so an agent can separate it from the single-write sibling without opening the schema.

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?

Guidance is concrete: expressions can be set inline instead of calling set_expression per parameter, override_expression=True is the escape hatch when expressions or links block a literal write, and run_callbacks=True is prescribed for the unlock-then-write case. What's missing is an explicit statement of when to prefer this over set_parameter (single write) beyond the implied batching.

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