Skip to main content
Glama
Sign In
Houdini MCP

Houdini MCP

by beatreichenbach
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

set_keyframes

Batch-set multiple keyframes on a Houdini parameter by providing the node path, parameter name, and keyframe list to automate animation setup.

Instructions

Batch-set multiple keyframes on 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>",
      "keyframes": "<keyframes>"
    },
    "name": "set_keyframes"
  }
}

Input Schema

NameRequiredDescriptionDefault
keyframesYes
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, and it discloses almost nothing: it does not say whether existing keyframes are replaced or merged, what happens on partial failure of a batch, whether the parameter must already be keyable, or what permissions are needed. 'Set' does correctly signal a mutation, but no consequences of that mutation are described.

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?

A single front-loaded sentence with no wasted words, which is structurally sound. However, the brevity here reflects under-specification rather than disciplined concision, since essential behavioral and parameter detail is simply absent.

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?

For a mutating, batch-structured tool with no annotations, no output schema, zero parameter documentation, and an untyped array of nested objects, the description is far too thin for an agent to call it correctly. Return values need not be explained given no output schema, but the batch semantics and item structure must be.

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 all three required parameters, and the description compensates only minimally by implying that parm_name refers to 'a parameter'. The keyframes array is an opaque list of objects with additionalProperties true and no item schema, and nothing explains whether items carry time/value pairs, interpolation, or ordering. Node path format and failure modes are likewise unexplained.

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?

States a specific verb and resource: 'Batch-set multiple keyframes on a parameter.' The word 'Batch' and the plural 'keyframes' implicitly distinguish it from the single-item sibling set_keyframe, and the 'on a parameter' clause names the target. It stops short of naming the sibling explicitly, but the operation and scope are unambiguous.

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 statement of when to use this tool versus set_keyframe, no prerequisites, and no exclusions. An agent must infer from the word 'Batch' alone that this is the multi-keyframe variant, so guidance is present only by implication.

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