Skip to main content
Glama

render_scene

Render the current Blender scene frame with configurable engine, samples, resolution, and output path for quick visual verification.

Instructions

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

Input Schema

NameRequiredDescriptionDefault
engineNo
samplesNo
output_pathNo
write_stillNo
resolution_percentageNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

D1.8/5.0
Behavior1/5

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

No annotations are supplied, so the description carries the full behavioral burden, and it discloses nothing. It does not state whether a file is written to disk, whether the scene state is modified, what permissions or engine settings are needed, or what happens when write_still is true.

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 sentence is short and front-loaded, but its brevity here reflects under-specification rather than efficiency. A single four-word clause cannot carry the weight required by a five-parameter render tool.

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

Completeness1/5

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

The tool takes five optional parameters with zero documented semantics, has no annotations, and performs a side-effecting render operation, yet the description addresses none of this. The existence of an output schema excuses only return-value explanation, not the missing parameter and behavior detail.

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

Parameters1/5

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

There are 5 parameters at 0% schema description coverage, and the description explains none of them. Engine, samples, output_path, write_still, and resolution_percentage all remain opaque, so the text adds no meaning beyond bare parameter names and defaults.

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

Purpose3/5

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

"Render the current frame" states a concrete verb (render) and resource (current frame), so the basic action is identifiable. However, it offers no differentiation from siblings such as render_preview, render_final, render_animation, or capture_render, so an agent cannot tell which render variant this is.

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 when-to-use guidance and no mention of alternatives or prerequisites. The single sentence implies only that a frame will be rendered, leaving the agent to guess how this differs from any of the many other render/capture siblings.

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