Skip to main content
Glama
Sign In
Houdini MCP

Houdini MCP

by beatreichenbach
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

create_material

Creates a material in /mat with configurable surface properties like base color, metallic, roughness, and opacity, enabling Houdini MCP clients to set up shading.

Instructions

Create a material in /mat with configurable surface properties.

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": "create_material"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNo
opacityNo
mat_typeNoprincipled
metallicNo
roughnessNo
base_colorNo

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?

With no annotations at all, the description carries the full disclosure burden. It does not say whether a node is written into the scene, what happens on name collision, what mat_type values exist beyond the default, or whether anything is destructive.

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 sentence with no filler and the target path front-loaded, but its brevity comes from under-specification rather than economy of expression.

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?

A 6-parameter mutation tool with no annotations, no output schema, and no parameter documentation needs far more than one sentence. An agent cannot know argument constraints or side effects from this definition.

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?

All 6 parameters have 0% schema description coverage — only titles and defaults. The phrase 'configurable surface properties' gestures at metallic/roughness/base_color/opacity but gives no ranges, formats, or meaning for name and mat_type, so it barely compensates for the schema gap.

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 concrete verb and resource ('Create a material') plus the target location ('/mat'), which lets an agent distinguish it from assign_material and get_material_info. It does not explicitly differentiate itself from create_material_network, so it falls short of 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 use this versus create_material_network (network creation) or assign_material (binding to a prim). The agent must infer that 'create in /mat' means a standalone material asset, and no prerequisites or exclusions are given.

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