Skip to main content
Glama
Show2Instruct

Bonsai MCP

get_viewport_screenshot

Read-only

Capture the Blender 3D viewport as an inline image. Optionally set view direction and fit mode to frame content.

Instructions

[QUERY] Capture the Blender 3D viewport and return the image inline. Optionally aim the viewport first: view sets the direction (top/bottom/front/back/left/right = orthographic axis views, 'iso' = perspective isometric, 'camera' = scene camera) and fit frames the content ('all' or 'selected'). The render is downscaled so the longest edge fits max_size (default 800 px) and encoded as JPEG by default, keeping the response safely under MCP size limits. Scene render settings are restored afterwards; the viewport orientation persists.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
fitNoFrame content before capturing: 'all' = everything, 'selected' = current selection. Combines with view.
viewNoAim the viewport before capturing. Axis names give orthographic views; 'iso' a perspective isometric; 'camera' the scene camera. Omit to keep the current orientation.
formatNo'jpeg' (default, small) or 'png' (lossless, large).jpeg
qualityNoJPEG quality. Ignored for png.
max_sizeNoLongest image edge in pixels. The render is only downscaled, never upscaled. Values above ~1200 with format='png' may exceed the response size cap.
max_objectsNoCap for include_objects; largest boxes are kept.
include_objectsNoAlso return, as text, screen-space 2D bounding boxes keyed by GlobalId for objects in frame (normalized 0-1, origin top-left). Use this for spatial reasoning when the image channel is unavailable or for grounding what the image shows.
Behavior4/5

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

Annotations already declare readOnlyHint and destructiveHint. The description adds context about scene render settings being restored, viewport orientation persisting, and downscaling/encoding to stay under size limits. This goes beyond annotations, but could mention any potential side effects like temporary view changes.

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?

The description is a single, well-structured paragraph that front-loads the core purpose, then details optional behaviors and rendering specifics. Every sentence is informative without redundancy.

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

Completeness5/5

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

Given the tool's complexity (7 parameters, optional view/fit, encoding, bounding boxes), the description covers all aspects adequately. It explains input, behavior, and output (image inline + optional bounding boxes) even without an output schema.

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

Parameters4/5

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

Schema coverage is 100%, but the description enriches parameter meaning: e.g., 'view' and 'fit' combine, 'max_size' only downscales, 'quality' ignored for png, 'include_objects' provides spatial reasoning info. This adds value beyond the schema definitions.

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 clearly states it captures the Blender 3D viewport and returns the image inline. It specifies the optional view aiming and fit parameters. Among sibling tools, none offer screenshot functionality, so it is well-distinguished.

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

Usage Guidelines4/5

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

The description explains when to use each optional parameter (view and fit) and their effects. It implies usage for visual context, but does not explicitly state when not to use it or provide direct alternatives. However, siblings are sufficiently different to avoid confusion.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Show2Instruct/bonsai-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server