Skip to main content
Glama
ChengZiiii

opera-houdini-mcp

by ChengZiiii

get_node_info

Retrieve detailed info about a Houdini node: path, type, counts, parameters, errors/warnings, and input connections. Optionally compact output or force node cook before reading.

Instructions

获取节点的详细信息。

参数说明:
- node_path: 目标节点路径。
- include_errors: 可选,是否包含 errors / warnings 字段,默认 True。
- force_cook: 可选,读取前是否调 node.cook(force=True),默认 False。
- include_input_details: 可选,是否包含每个 input 的详细连接
  (用 node.inputConnectors() 一次性取),默认 False。
- compact: 可选,是否仅返精简字段 path/type/counts(不含 parameters /
  errors / warnings),默认 False。

返回 dict:compact=True 时仅含 path / type / children_count / input_count
/ output_count 五项;否则包含完整字段(详见 _node_info.get_node_info)。
节点不存在时函数会抛 ValueError,bridge 透传 error envelope 不静默吞错。

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
ctxYes
compactNo
node_pathYes
force_cookNo
include_errorsNo
include_input_detailsNo
Behavior5/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It does this exceptionally well by explaining defaults for all optional parameters, the side effect of force_cook (calls node.cook(force=True)), the compact return structure, and error propagation (throws ValueError, bridge passes through error envelope). This goes well beyond a generic 'get' tool.

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 well-structured with a heading, bullet-pointed parameter list, and separate sections for return format and error behavior. Every sentence adds value, and there is no redundant or filler content.

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 parameters and error behavior well, but it does not enumerate the full (non-compact) return fields, instead referencing an internal function '_node_info.get_node_info' which is inaccessible to the agent. Without an output schema, this leaves the return format incomplete. Additionally, there is no usage context relative to sibling tools.

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

Parameters5/5

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

Schema coverage is 0%, and the description compensates by explaining every parameter's meaning and default value: node_path, include_errors, force_cook, include_input_details, and compact. This adds essential meaning beyond the bare schema, making parameter usage unambiguous.

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?

The description clearly states '获取节点的详细信息' (get detailed information of a node), providing a specific verb and resource. However, it does not explicitly distinguish this tool from sibling tools like get_geometry_info or explain_node, so the purpose is clear but lacks sibling differentiation.

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?

The description provides no guidance on when to use this tool versus alternatives. It only describes parameters and return behavior, leaving the agent to infer usage context without any exclusions or alternative recommendations.

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