Skip to main content
Glama

capture_camera_view

Capture an image from the active or named Blender camera to visually verify 3D scenes and camera framing. Optionally set a maximum image size.

Instructions

Capture from the active or named camera.

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

Input Schema

NameRequiredDescriptionDefault
cameraNo
max_sizeNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.4/5.0
Behavior2/5

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

With no annotations, the description carries the full disclosure burden and supplies almost none of it. It does not say whether the capture is written to disk or returned inline, what format or resolution results, whether it is read-only, or what happens if no camera is active.

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, front-loaded sentence with no filler or redundancy. It is efficient, though the terseness comes at the cost of the missing details scored elsewhere rather than from good editing.

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 the definition still leaves key operational facts unstated: where the capture goes, what max_size controls, and how this differs from the many sibling capture tools. For a tool in a crowded capture family with zero annotation and zero schema coverage, this is insufficient.

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% across two parameters. The phrase 'active or named camera' does usefully explain that omitting camera falls back to the active camera, but max_size is left entirely undefined — no units, no default behavior, no effect on output. Half the parameters remain opaque.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The verb+resource pair 'Capture from ... camera' identifies the operation, and 'active or named' hints at scope. However, 'capture' is ambiguous (still image? render? viewport grab?) and the description does nothing to separate it from siblings such as capture_viewport, capture_render, or camera_view.

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 guidance at all: no condition distinguishing this from capture_viewport, capture_render, capture_scene_preview, or camera_view. The 'active or named' phrasing implies a selection mode but never tells the agent which mode to prefer or when.

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