Set the global frame range in Houdini by providing start and end frame values for playback, simulation, or rendering.
Set the global frame range.
Args: start: Start frame. end: End frame.
| Name | Required | Description | Default |
|---|---|---|---|
| end | Yes | ||
| start | 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?
Annotations are absent, so the description carries the full burden. It implies a mutation but says nothing about whether the change is persisted to the scene, how it interacts with existing keyframes/playback range, or whether it requires a connected Houdini session.
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?
Front-loaded single-sentence purpose followed by a terse Args list; nothing extraneous. Slightly boilerplate in the Args repetition but efficient overall.
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?
A mutation tool with no annotations, no output schema, and 0% schema coverage should explain side effects and the relationship to playback/keyframe state. Instead it provides only the minimal restated signature.
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. The Args block only restates the parameter titles ('start: Start frame', 'end: End frame') with no units, frame-rate assumptions, ordering constraints, or valid range.
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?
States a concrete verb and resource ('Set the global frame range'), which is clearly distinct from keyframe/frame-read siblings. However, it does not distinguish itself from the sibling set_playback_range, leaving the boundary between the two range-setting tools to inference.
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 prerequisites, and no mention of the sibling set_playback_range or set_frame that an agent could confuse this with. The agent must guess whether this affects the whole scene or just playback.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.