Skip to main content
Glama
ChengZiiii

opera-houdini-mcp

by ChengZiiii

parse_hip_offline

Parse Houdini .hip/.hiplc/.hipnc files offline to inspect nodes, connections, postits, and netboxes without launching Houdini.

Instructions

离线 best-effort 解析 .hip/.hiplc/.hipnc(bridge-local,无 Houdini 连接)。

本工具 **不建立 Houdini TCP 连接、不 import hou**,直接在 bridge 进程
内按真实 legacy cpio/odc entry 流式读取 archive(magic 070707、76 字节
header),best-effort 提取节点 type、def comment/position/connections、
可选 parm 序列化原始值、postit 文本与 netbox label,并对不可信输入施加
file/entry/section/total/node 五类硬限额(``max_depth`` 仅裁输出树)。

与 ``serialize_scene`` / ``get_node_info`` 互补:那两个面向**在线** Houdini
连接的实时节点树查询;本工具面向**离线**文件审计(如查看一个 .hip 里
有哪些节点/连线,而不必启动 Houdini)。

参数说明:
- file_path: ``.hip``/``.hiplc``/``.hipnc`` 文件路径;其他扩展名返回
  ``unsupported_extension``。
- include_params: 可选,True 时每节点附 ``parameters``(archive 中序列化
  的原始 parm 文本,**不求值、不比较默认、不保证动画/表达式完整**)。
- max_depth: 可选,输出 ``structure`` 树深度,clamp 到 ``[1,64]``;
  flat ``nodes``/``connections`` 不受影响。

返回统一 envelope:``status``(success/error)、``file_path``、
``save_version``(从 ``.variables`` 的 ``_HIP_SAVEVERSION`` 明确提取,
不可得为 null)、``nodes``(flat)、``connections``、``postits``、
``netboxes``、``structure``(depth-clipped 树)、``metadata``(含
complete_entries/bytes_consumed/trailer_seen/duplicate_entries/
skipped_sections/limits)。error 形如
``error:{code,message,details}`` 并尽可能附 partial(trailer_seen=false,
不含截断 body)。error code:unsupported_extension / invalid_archive /
corrupt_archive / truncated_archive / resource_limit_exceeded /
hip_not_found / hip_io_error。success 与 error-partial 均**过**
``apply_response_cap``。

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
ctxYes
file_pathYes
max_depthNo
include_paramsNo
Behavior5/5

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

With no annotations provided, the description fully discloses behavioral traits: it states it does not establish a TCP connection or import hou, streams using legacy cpio/odc entry format, applies five hard limits for untrusted input, only clips output tree with max_depth, and includes caveats like '不求值、不比较默认、不保证动画/表达式完整'. It also explains partial error responses and the apply_response_cap behavior, far exceeding baseline expectations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is detailed but highly structured: first the core behavior and safety, then the differentiation from siblings, followed by parameter notes and the return envelope with error codes. Each sentence carries substantive information with no filler, and the front-loaded opening makes the tool's purpose immediately clear.

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

Completeness5/5

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

Given the complexity of the tool (4+ parameters, no output schema, no annotations), the description covers all necessary aspects: operation mode, extraction targets, limits, parameter semantics, return envelope fields, error codes, and partial-result behavior. It is self-sufficient for an agent to understand, invoke, and interpret results correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema provides no descriptions (0% coverage), so the description compensates by explaining file_path (extension restriction, unsupported_extension error), include_params (raw parm text, no evaluation), and max_depth (clamped to [1,64], affects only structure tree). However, the required 'ctx' parameter is not explained at all, which is a minor gap given the detailed coverage of the other three parameters.

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 opens with a specific verb+resource+scope: '离线 best-effort 解析 .hip/.hiplc/.hipnc(bridge-local,无 Houdini 连接)' clearly stating it parses offline Houdini archive files without a Houdini connection. It also distinguishes itself from siblings by explicitly naming serialize_scene/get_node_info as online alternatives, making the purpose unambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives explicit when-to-use guidance: '与 serialize_scene / get_node_info 互补:那两个面向在线 Houdini 连接的实时节点树查询;本工具面向离线文件审计' — directly contrasting with online tools and prescribing offline file auditing as the intended use case. This provides clear alternatives and context.

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