Skip to main content
Glama

capture_viewport

Capture the Blender viewport as an image, optionally overriding view, shading, or size, to inspect and verify 3D scenes visually.

Instructions

Capture the viewport with optional view/shading overrides.

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
viewNo
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 supplied, so the description carries the full burden. It does not say whether the capture writes a file, returns image data, affects scene state, requires an active Blender session, or what 'view/shading overrides' do to the result — all material for a capture operation.

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?

A single front-loaded sentence with no filler. Its brevity is efficient, though it borders on under-specification rather than true 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 described, but three fully undocumented parameters and zero annotation coverage leave too much unexplained. For a 3-parameter capture tool, the definition should say what the parameters accept and what the capture produces or where it goes.

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%, so the description must compensate. It names 'view' and 'shading' but adds no meaning — no accepted values, no format, no indication of how an override differs from the current viewport setting — and 'max_size' is not mentioned at all.

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?

Names a specific verb ('Capture') and resource ('the viewport'), so an agent knows it produces a viewport image. It does not distinguish itself from siblings such as get_viewport_screenshot or capture_camera_view, leaving ambiguity about which capture tool 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?

The only usage signal is 'optional view/shading overrides', which hints at a variant behavior but never states when to choose this tool over the many sibling capture tools. No prerequisites, no exclusions, no context about what a 'viewport' capture includes versus a camera or scene preview.

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