Batch-set Houdini keyframes atomically: validates all entries first, writes in one undo group, and reports set count.
批量关键帧写入（PR 19，场景写，可 undo）。
``keyframes`` 为 list，每项 dict 至少含 ``path`` /
``parameter`` / ``frame`` / ``value``；任一项无效则**整调
用**失败、零写入（在 server 上层预校验拒绝）。全部有效时
在单个 ``hou.undos.group`` 内逐项写入并返回 ``set_count`` /
``requested``。错误列表同样受 server 端 ``apply_response_cap``
截断保护。
| Name | Required | Description | Default |
|---|---|---|---|
| ctx | Yes | ||
| keyframes | Yes |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
在无注释的情况下，详细披露了原子性（任一无效则整调用失败、零写入）、undo分组、返回set_count/requested以及错误截断机制，使代理能清楚预期调用效果。
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
总体简洁，关键信息集中。但'PR 19'这类未解释的引用对代理可能无帮助，略增加理解成本。
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
覆盖了原子性、undo、返回值等关键行为，但缺失输入序列化方式和ctx说明，且存在schema类型矛盾，对无输出schema的工具而言完整性有缺口。
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
keyframes参数描述了list及必填字段，但schema定义keyframes为string，两者存在明确类型矛盾；ctx参数未做任何说明，且无schema描述，导致代理难以可靠构造参数。
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
描述明确说明是批量关键帧写入，且提及场景写、可undo等，与set_keyframe等兄弟工具在功能和规模上有明显区分。
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
描述了批量写入的适用场景（批量关键帧），但未明确给出与set_keyframe的对比或排除性说明。不过'批量'本身就隐含了使用情境。
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
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