Retrieve primitives modified by the last LOP node cook for a Houdini LOP node path. Use it to inspect which prims changed after a cook.
Get prims modified by the last LOP node cook.
Args: node_path: LOP node path.
| Name | Required | Description | Default |
|---|---|---|---|
| node_path | Yes |
Changes observed during successful MCP inspections.
v2.24.1Input schema / additionalPropertiesAdded value: +falsev0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full behavioral burden. 'Get' implies read-only behavior and names the data source, but return format, permissions, side effects, and cook prerequisites are omitted.
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?
Two sentences, front-loaded purpose, and zero waste. The compact args section is appropriate for a one-parameter tool.
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?
For a simple one-parameter read tool, the description is minimally adequate. However, with no output schema and no annotations, it could clarify return values and safety/behavioral context.
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?
Schema description coverage is 0%, so the description must compensate. It adds 'LOP node path' context beyond the schema's 'Node Path' title, but does not specify expected path format or examples.
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?
Specific verb 'Get' and resource 'prims', scoped to 'last LOP node cook'. The purpose is clear, though it does not explicitly distinguish itself from generic prim-listing siblings like get_prims.
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?
No when-to-use guidance, no alternatives, and no exclusions. The LOP-cook context implies usage, but the description never states when an agent should choose this over other prim or USD tools.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.