Skip to main content
Glama

capture_render

Capture or retrieve the current Blender render preview for visual verification; use max_size to cap image dimensions.

Instructions

Capture or return the latest render preview.

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

Input Schema

NameRequiredDescriptionDefault
max_sizeNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.4/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden and discloses almost nothing. It does not state whether capturing triggers an actual render (potentially slow or state-changing), whether it requires an existing render, or what the returned preview represents. Only the bare existence of two possible behaviors is conveyed.

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

Conciseness3/5

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

It is a single short sentence, so nothing is wasted, but the brevity comes at the cost of substance rather than from tight editing. The core action is front-loaded, yet the sentence hedges with 'or' instead of resolving the ambiguity.

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?

An output schema exists, so return values need not be spelled out, which lightens the burden. However, for a capture/render tool with an undocumented parameter and an unresolved capture-vs-return distinction, the description is not complete enough to invoke confidently.

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% for the single parameter max_size, and the description never mentions it. Units (pixels? bytes?), effect (downscaling? output cap?), and default behavior when null are all undocumented in both schema and prose.

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?

The description names a resource (render preview) and an action (capture), but 'Capture or return the latest' presents two distinct behaviors without clarifying which applies when or how the mode is selected. Against siblings like capture_camera_view, render_preview, and get_render_result, an agent cannot confidently tell what this tool uniquely does.

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 guidance on when to use this versus render_preview, get_render_result, or capture_scene_preview, and no explanation of when it captures fresh versus returns cached. The 'or' leaves the invocation decision entirely to inference.

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