Skip to main content
Glama
Sign In
Houdini MCP

Houdini MCP

by beatreichenbach
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

setup_flip_sim

Create a FLIP fluid simulation network from source geometry in Houdini, with configurable domain, particle separation, and source object.

Instructions

Build a FLIP fluid simulation network from source geometry.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "setup_flip_sim"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoflip_sim
domainNobox
source_geoNo/obj/geo1/sphere1
particle_sepNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.7/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 disclosure burden. 'Build' implies a scene mutation that creates multiple nodes, but nothing is said about what gets created, whether it overwrites prior work, required context (e.g., a valid source geo), or what the call returns. That is a significant gap for an unscoped mutation tool.

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?

A single, front-loaded sentence with no wasted words. It is efficient, though the brevity contributes to the informational gaps elsewhere rather than being a virtue in itself.

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?

Building a whole simulation network is a complex, multi-node operation with no annotations, no output schema, and four undocumented parameters. The one-line description does not cover enough for an agent to call it confidently or anticipate side effects.

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 four parameters. The phrase 'source geometry' loosely gestures at source_geo, but name, domain, and particle_sep are entirely unexplained in both schema and description, so an agent cannot know the meaning or valid values of particle_sep or domain.

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?

Specific verb and resource: 'Build a FLIP fluid simulation network from source geometry.' The domain word 'FLIP' distinguishes it from the pyro, RBD, and Vellum setup siblings, so an agent can pick the right one without opening a schema. It stops short of explicitly stating the sibling relationship, keeping it just under 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?

No guidance on when to prefer this over setup_pyro_sim/setup_rbd_sim/setup_vellum_sim, no prerequisites, and no note about whether existing networks are replaced. The agent must infer selection purely from the word 'FLIP'.

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