Skip to main content
Glama

set_current_frame

Sets the current frame in Blender to a specified frame number, letting AI clients position animation playback and scrub timelines precisely.

Instructions

Set the current frame.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "frame": "<frame>"
    },
    "name": "set_current_frame"
  }
}

Input Schema

NameRequiredDescriptionDefault
frameYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2/5.0
Behavior2/5

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

Annotations are absent, so the description carries the full burden, and it discloses almost nothing: not that this mutates scene state, not what happens to the previously current frame, not whether it triggers any evaluation, and not whether the change is persisted in undo history.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The single sentence is short but not well-structured conciseness: it front-loads nothing useful and omits content an agent needs. Brevity here comes from under-specification rather than efficiency.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return values need not be explained. But for a one-parameter state-mutating tool with zero annotation coverage and no schema descriptions, the definition should at minimum state the valid frame domain and side effects; it does neither.

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?

Schema description coverage is 0% and the description adds no meaning: it does not say whether frames are 1-indexed, what the valid range is relative to frame_start/frame_end, or what happens for out-of-range values. Only the parameter's self-evident name "frame" carries meaning.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Set the current frame." restates the tool name with a synonym and adds nothing: no object, no scene/timeline scope, and no distinction from neighbors such as set_keyframe or set_animation_range that also touch frame-related state.

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?

There is no guidance on when to call this versus alternatives, nor any stated prerequisite (e.g., that a scene or animation context must exist). The imperative verb hints at usage but nothing is stated explicitly.

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