Blender Bridge

Capture screenshot artifact

take_screenshot_only

Capture a screenshot artifact through the local bridge and return only URL/metadata, without inline base64 or image attachment. Use this for batch/reference screenshots when the model does not need the image embedded in the tool result.

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

Input Schema

Name	Required	Description
`width`	No	Requested screenshot width in pixels.
`format`	No	Image encoding for the captured screenshot: PNG or JPEG.
`height`	No	Requested screenshot height in pixels.
`source`	No	Use viewport for the current 3D view; camera requests the active scene camera view.
`quality`	No	Requested image-encoding quality, from 20 to 100.

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedOct 23, 2026

addedInput schema / properties / format / description

Added value: +"Image encoding for the captured screenshot: PNG or JPEG."

addedInput schema / properties / height / description

Added value: +"Requested screenshot height in pixels."

addedInput schema / properties / quality / description

Added value: +"Requested image-encoding quality, from 20 to 100."

addedInput schema / properties / source / description

Added value: +"Use viewport for the current 3D view; camera requests the active scene camera view."

addedInput schema / properties / width / description

Added value: +"Requested screenshot width in pixels."

First observedOct 23, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare the safety profile: not read-only, not destructive, not idempotent, and closed-world. The description adds meaningful behavioral context by explaining that the result contains only URL/metadata and no inline image payload, which is the key operational distinction for an agent.

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 two focused sentences with no wasted text. The return-format constraint and the batch/reference use case are front-loaded and easy to scan.

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?

The tool has no output schema, and the description compensates by stating exactly what is returned: URL/metadata rather than an embedded image. It also identifies the local-bridge dependency, though it could say more about failure conditions or bridge availability requirements.

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 coverage is 100%, and all five parameters have descriptive entries including ranges and enums. The description does not add parameter-level guidance beyond the schema, so the baseline score of 3 is appropriate.

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 gives a specific verb and resource: 'Capture a screenshot artifact through the local bridge.' It also immediately distinguishes this tool from the normal screenshot path by stating it returns only URL/metadata, without inline base64 or image attachment.

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?

It provides a clear usage condition: 'Use this for batch/reference screenshots when the model does not need the image embedded in the tool result.' The inverse condition is implied, but the description does not explicitly name the alternative screenshot sibling or state when not to use this tool.

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?