Skip to main content
Glama
3bdull4h2008

Blender MCP Ultra

by 3bdull4h2008
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

get_viewport_screenshot

Capture a Blender viewport screenshot via GPU offscreen rendering, with adjustable size, overlays, camera view, and render engine.

Instructions

Take a high-quality viewport screenshot using GPU offscreen rendering.

Args: filepath: Path to save the PNG. If empty, returns base64 only. width: Output width in pixels. height: Output height in pixels. include_overlays: Include viewport overlays (grid, outlines, etc.). camera_view: Render from the active camera's perspective. render_engine: Override render engine ('BLENDER_EEVEE', 'BLENDER_CYCLES', 'BLENDER_WORKBENCH').

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
widthNo
heightNo
filepathNo
camera_viewNo
render_engineNo
include_overlaysNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv3.0.0

TDQS

A3.9/5.0
Behavior3/5

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

No annotations, so description must disclose behavior. It mentions GPU offscreen rendering, implying no screen display. But it doesn't state whether it's read-only, side effects, or return value beyond base64 when filepath empty. Partial 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?

Concise with a clear lead sentence and an organized Args block. No unnecessary text.

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?

The description covers the parameters well but lacks details on the return value when filepath is provided, and does not mention any prerequisites or limitations. Given no output schema, some return information would be helpful, but it's still fairly complete.

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

Parameters5/5

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

Schema has 0% description coverage, but the description provides a detailed Args section explaining each parameter, including the filepath behavior (base64 if empty) and render_engine override. This fully compensates for the schema's lack of descriptions.

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?

States a specific verb and resource: 'Take a high-quality viewport screenshot' with GPU offscreen rendering. It clearly distinguishes from siblings like get_viewport_screenshot_comparison and get_render_preview.

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 tool vs alternatives. It does not mention any exclusions or comparisons to siblings. The description is purely functional without context on selection.

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