Blender Bridge

Panel: capture viewport

view_capture

App-only adapter for the Blender Bridge panel's capture and viewpoint controls. Starts a fresh screenshot operation in the receiving Blender and stores its preview; this can return operation progress before completion. view selects the current viewport, camera or a requested viewpoint and defaults to viewport. auto marks a panel-triggered automatic capture rather than a user click. Requires account access and a working Blender. Use view_latest to read an existing preview without capture; models should use take_screenshot for a fresh image.

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

Input Schema

Name	Required	Description	Default
`auto`	No	Mark this request as an automatic panel capture when true.
`view`	No	Capture source or viewpoint; omitted defaults to viewport.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 23, 2026

addedInput schema / properties / auto / description

Added value: +"Mark this request as an automatic panel capture when true."

addedInput schema / properties / view / description

Added value: +"Capture source or viewpoint; omitted defaults to viewport."

First observedOct 23, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, and idempotentHint=false, and the description is consistent with those by saying it starts a fresh capture and stores a preview. It adds useful context beyond annotations: it may return operation progress before completion and requires account access and a working Blender. It does not fully describe error modes or the exact preview return behavior, so it is strong but not exhaustive.

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 front-loaded with the tool's purpose and operation, then covers parameters, prerequisites, and alternatives in compact sentences. Each sentence contributes operational context without unnecessary repetition.

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?

For a two-parameter capture tool with no output schema, the description covers the essential behavior: it starts a capture, stores a preview, may return progress, requires account/Blender access, and points to view_latest for reading an existing preview. It could be slightly more explicit about what is returned while the operation is still in progress, but it is largely complete.

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

Parameters3/5

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

Schema description coverage is 100%, so both parameters are already fully documented in the schema. The description restates the view default and explains that auto marks a panel-triggered automatic capture rather than a user click, adding only marginal meaning beyond the structured fields.

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 states a specific verb and resource: it starts a fresh screenshot operation in the receiving Blender and stores its preview. It also explicitly distinguishes this app-panel capture adapter from take_screenshot and view_latest, so an agent can identify its role without opening sibling schemas.

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

Usage Guidelines5/5

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

It gives explicit routing guidance: use view_latest to read an existing preview without capture, and models should use take_screenshot for a fresh image. That makes the when-to-use-this-versus-alternatives condition very clear.

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

All Blender Bridge tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?