Skip to main content
Glama
Sign In
blender-mcp

blender-mcp

by kleer001
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

set_frame_range

Idempotent

Define the animation frame range by setting the start and end frames for the current scene.

Instructions

Set the scene frame range (start and/or end frame).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "set_frame_range"
  }
}

Input Schema

NameRequiredDescriptionDefault
endNo
startNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

With only an idempotentHint annotation, the description carries the burden of explaining behavior. It states that start and/or end frames can be set, but does not clarify the effect of null values (e.g., whether null means the existing value is kept). This is a key behavioral aspect that is left to inference.

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 a single sentence with no fluff, front-loading the verb and purpose. Every word contributes to understanding the core function.

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?

Given the tool's simplicity and the presence of an output schema, the description is mostly sufficient. However, it leaves out null-value behavior and does not differentiate from sibling set_playback_range, which is a completeness gap. The phrase 'scene frame range' provides some context but not enough to fully disambiguate.

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

Parameters2/5

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

The input schema has no parameter descriptions (0% coverage), so the description must compensate. It mentions that start and/or end frames can be set, which aligns with the schema, but it does not explain the semantics of null values or any constraints like end > start. The parameter meaning is mostly derived from the names.

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 that the tool sets the scene frame range, specifying both start and end frames. It uses a specific verb ('set') and resource ('scene frame range'), making the purpose clear. However, it does not distinguish from sibling set_playback_range, which may be used for similar purposes.

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?

No usage guidance is provided. The description does not mention when to use this tool versus alternatives like set_playback_range or set_frame, nor does it exclude any cases. Without this, an agent may select the wrong tool.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools