Skip to main content
Glama
TechBot_Blender_MCP

TechBot_Blender_MCP

by bharatnextai

capture_viewport

Capture a bounded PNG snapshot of the 3D viewport or active camera without changing scene state, returning base64 image data for inspection or documentation.

Instructions

Capture a bounded visual snapshot of the 3D viewport or active camera without mutating scene state or persistent render settings. Returns base64 PNG data.

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_viewport"
  }
}

Input Schema

NameRequiredDescriptionDefault
modeNoCapture viewpoint: active interactive 3D viewport ('VIEWPORT') or scene active camera ('CAMERA').VIEWPORT
viewNoViewpoint projection or angle: 'CURRENT' (default), 'FRONT', 'SIDE', 'TOP', or 'PERSPECTIVE'. Supported in interactive 3D Viewport or via directional camera capture.CURRENT
widthNoImage resolution width in pixels (bounded 64 to 2048).
formatNoOutput image format (PNG only).PNG
heightNoImage resolution height in pixels (bounded 64 to 2048).
samplesNoRender sample count for capture (bounded 1 to 64).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.6/5.0
Behavior4/5

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

With no annotations present, the description does real work: it discloses that scene state and persistent render settings are not mutated, and that the return payload is base64 PNG. Gaps remain around cost/latency (does sample count make this slow?) and failure modes when no viewport or camera exists, which matter more without annotation coverage.

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 action and target, followed immediately by the non-mutation guarantee and return type. No filler, no restatement of the title.

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 six-optional-parameter read-style capture tool with full schema coverage and no output schema, the description covers purpose, safety profile, and return encoding. What is missing is operational context: cost of higher sample counts and behavior when the requested view is unavailable.

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 coverage is 100%, so all six parameters are already documented with enums, bounds, and defaults. The description adds only the word 'bounded', which restates the schema's min/max constraints rather than clarifying mode/view interplay or sample-count tradeoffs. Baseline 3 is appropriate when the schema carries parameter meaning.

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?

States a specific verb and resource ('Capture a bounded visual snapshot of the 3D viewport or active camera') and even names the two capture targets that map to the mode enum. It implicitly separates itself from render/configure siblings by framing this as a bounded snapshot, though it never names an alternative outright.

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 or when-not-to-use guidance. The description never says to prefer this over a full render or configure_camera, nor does it mention preconditions such as needing an active viewport or what happens in headless mode. The reader must infer usage purely from the purpose statement.

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