Skip to main content
Glama
ChengZiiii

opera-houdini-mcp

by ChengZiiii

execute_hscript

Run HScript command strings in Houdini to perform built-in operations such as ls, cd, and opset, and receive stdout/stderr results.

Instructions

在 Houdini 中执行 HScript 命令字符串。

HScript 是 Houdini 的传统脚本语言(与 Python/HScript 两套接口并存),
适合执行 `ls`、`cd`、`opset` 等内建命令。调用结果以 stdout / stderr
形式返回。

参数说明:
- code: HScript 命令字符串(如 "cd /obj; ls")。空字符串 / 纯空白
  会被服务端拒绝并返回错误。

返回字符串包含 stdout / stderr 两段;连接或服务端出错时返回
"Error (...): ..." 形式的提示。

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
ctxYes
codeYes
Behavior3/5

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

With no annotations, the description carries the full burden. It discloses the stdout/stderr return format, rejection of empty/whitespace code, and error message format. However, it does not mention potential side effects of arbitrary command execution, permissions, or execution context beyond 'in Houdini', leaving significant behavioral aspects undisclosed.

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?

The description is well-structured with separate sections for the command and parameter details, includes a concrete example, and wastes no words. It could be slightly tighter but is effectively concise.

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

Completeness3/5

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

The description covers the core purpose, input, and output format, but lacks details on `ctx`, safety considerations, command execution limits, and error conditions beyond the generic error message. For an arbitrary command execution tool, this is only partially complete.

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%, so the description must document all parameters. It thoroughly explains `code` with an example and constraint, but completely omits `ctx`, which is required. Only half the parameters are documented, leaving a critical gap.

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 description clearly states the tool executes HScript command strings in Houdini, explicitly naming built-in commands like `ls`, `cd`, and `opset` as examples. It also distinguishes HScript from the Python interface, differentiating it from sibling execute_houdini_code.

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?

The description says HScript is suitable for executing built-in commands, which gives clear context for when to use this tool. However, it does not explicitly mention alternatives or exclusions (e.g., 'use execute_houdini_code for Python'), so it stops short of full guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/ChengZiiii/opera-houdini-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server