Skip to main content
Glama
Sign In
Houdini MCP

Houdini MCP

by beatreichenbach
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

execute_hscript

Executes HScript commands in Houdini so MCP clients can automate scene tasks, query data, and trigger custom workflows.

Instructions

Execute an HScript command in Houdini.

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": {
      "command": "<command>"
    },
    "name": "execute_hscript"
  }
}

Input Schema

NameRequiredDescriptionDefault
commandYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.4/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 behavioral burden and largely fails it: it does not mention that this executes arbitrary code in the live Houdini session, whether the operation mutates scene state, whether it is reversible, or what happens on command error. 'Execute' minimally implies side effects, but nothing about risk, permissions, or failure behavior is disclosed.

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 short sentence with zero filler and the operation stated up front. The brevity is efficient rather than padded, though the space saved is not spent on any useful detail.

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

Completeness1/5

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

For an arbitrary-code-execution tool with no annotations, no output schema, and an undocumented parameter, the description is far too thin. An agent cannot tell what the command string should look like, what is returned, or what risks accompany running code in the session.

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?

There is one required parameter with 0% schema description coverage, so the schema provides no meaning at all. The description adds nothing about the expected command syntax, whether it is a single statement or a full snippet, or how multi-line input is handled, leaving the sole parameter undocumented in both places.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description gives a verb ('Execute') and a resource ('an HScript command') plus the host application ('Houdini'), but it essentially restates the tool name execute_hscript with no added specificity. It does not distinguish this from the sibling execute_python, which is the obvious competing option for arbitrary scripting.

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 guidance on when to use HScript versus the sibling execute_python, nor any prerequisite or precondition. The only implied usage comes from the tool name itself, so an agent gets no routing help beyond the name.

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