Skip to main content
Glama
TechBot_Blender_MCP

TechBot_Blender_MCP

by bharatnextai

render_scene

Renders the active Blender scene to disk as a still image or animation sequence/video, with configurable frame range, output path, format, and camera selection.

Instructions

Render the active Blender scene to disk as a still image or animation sequence/video. Supports configurable render mode ('still' or 'animation'), target frame or frame range, custom output path, image format, and optional camera selection. Requires user approval and strictly verifies generated output files on disk.

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": "render_scene"
  }
}

Input Schema

NameRequiredDescriptionDefault
frameNoTarget frame number for still render. Defaults to current scene frame if omitted.
cameraNoOptional name of the camera object to render from. If omitted, uses the active scene camera.
task_idNoOptional task or workflow identifier.
approvedNoDEPRECATED / UNTRUSTED: Client-supplied approval flags in tool arguments are not trusted as proof of human consent.
frame_endNoEnding frame for animation render. Defaults to scene end frame if omitted.
frame_startNoStarting frame for animation render. Defaults to scene start frame if omitted.
output_pathNoCustom output file path or directory. If omitted, uses the scene's configured render filepath.
render_modeNoRender mode: 'still' for single frame or 'animation' for frame range sequence/video.still
output_formatNoOutput image format ('PNG', 'JPEG', 'OPEN_EXR', 'TARGA', 'TIFF'). If omitted, uses scene's configured format.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full burden and does add meaningful behavior: it requires user approval and verifies generated output files on disk, which are non-obvious gating and post-condition traits for a write operation. It stops short of stating overwrite behavior, failure handling, or what is returned when verification fails.

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?

Two sentences, front-loaded with the core action followed by the behavioral constraints. No filler or redundant phrasing; each clause carries distinct information.

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

Completeness4/5

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

For a nine-parameter mutation tool with no annotations and no output schema, the description covers purpose, modes, and the approval/verification contract adequately. It could say more about what happens to existing files at output_path and how verification failure surfaces, but nothing essential to a correct call is missing.

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

Parameters3/5

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

Schema description coverage is 100%, so all nine parameters are already documented with defaults and enums. The description only restates them at a high level (render mode, frame range, output path, format, camera) and adds no syntax, precedence, or default-resolution detail beyond the schema.

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

Purpose5/5

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

The description states a specific verb and resource ('Render the active Blender scene to disk') and enumerates the two output modes (still image vs. animation sequence/video). This clearly separates it from siblings like render_vse_sequence or configure_render_settings without the agent needing to open another schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage context is implied by the mode/format/path enumeration, but there is no explicit when-to-use guidance, no exclusions, and no mention of alternatives such as configure_render_settings (for setup) or inspect_render_output (for validation). The agent must infer routing from sibling names alone.

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