Set the animation frame range and frames per second for Blender scenes. Specify start and end frames, optionally adjust FPS to control playback timing.
设置帧范围与 fps。
| Name | Required | Description | Default |
|---|---|---|---|
| end | Yes | ||
| fps | No | ||
| start | Yes |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full burden of transparency. It does not mention side effects, like whether existing keyframes are affected, whether the change is immediate, or any potential destructive aspects. Minimal information is provided.
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?
The description is a single concise sentence with no redundant words. It is well-structured and quickly readable.
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 setter, the description covers the basic function but lacks details on usage context, parameter specifics, and potential effects. It is not fully complete but adequate for a minimal tool.
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?
The schema has no parameter descriptions (coverage 0%), but the description 'frame range and fps' gives a high-level meaning for start, end, and fps. It does not clarify details like inclusivity, units, or default behavior, so it adds only partial semantics.
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?
The description clearly states the action ('Set') and the resource ('frame range and fps'), which is specific and unambiguous. It distinguishes from related tools like set_current_frame by implying a range, though not explicitly naming alternatives.
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?
The description provides no guidance on when to use this tool versus alternatives, such as set_current_frame or other animation-related setters. It lacks any contextual conditions or prerequisites.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.