Skip to main content
Glama

get_viewport_screenshot

Capture the current 3D viewport as an image to visually verify models, shading, lighting, and scene state in Blender.

Instructions

Capture the 3D viewport as an image for visual verification.

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

Input Schema

NameRequiredDescriptionDefault
shadingNo
max_sizeNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.7/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden and largely fails to meet it. It does not say what image format is returned, whether the capture reflects the workbench vs rendered shading, whether the viewport must be open/active, or whether the operation has side effects or cost.

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

Conciseness4/5

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

One short sentence with no wasted words, and the core action is front-loaded. Its terseness is efficient but borders on under-specification rather than optimal conciseness.

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

Completeness2/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 explained, but the description leaves both input parameters undocumented and gives no behavioral context despite having no annotations to fall back on. For a capture tool with quality-affecting options, this is not enough for correct invocation.

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 two parameters ('shading' and 'max_size'), and the description never mentions either one. An agent must infer the meaning, valid values, and defaults of both parameters entirely on its own, which is a significant gap for a tool whose output quality depends on them.

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?

The description gives a specific verb ('Capture'), a specific resource ('the 3D viewport'), and the artifact produced ('as an image'), so an agent knows exactly what operation this is. It does not, however, differentiate itself from the sibling 'capture_viewport', leaving the agent to guess which of the two capture tools to pick.

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?

'for visual verification' hints at a use case but gives no explicit when-to-use, when-not-to-use, or prerequisite conditions. There is no guidance on how this differs from the sibling capture_viewport, which is the key decision the agent faces.

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