Skip to main content
Glama
Sign In
Blender MCP Plus

Blender MCP Plus

by lusilong
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

get_screenshot_of_area_as_image

Read-only

Capture a PNG screenshot of a specific Blender area by specifying its UI type, with an optional byte size limit for the returned image.

Instructions

Take a screenshot of a single Blender area and return it as a PNG image.

area_ui_type matches the area's ui_type.

size_limit_in_bytes caps the image size in bytes. Zero (the default) uses the MCP message size limit.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "area_ui_type": "<area_ui_type>"
    },
    "name": "get_screenshot_of_area_as_image"
  }
}

Input Schema

NameRequiredDescriptionDefault
area_ui_typeYes
size_limit_in_bytesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.3

TDQS

A4.4/5.0
Behavior4/5

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

The readOnlyHint annotation already covers safety, and the description adds useful behavior details: the result is a PNG image, size_limit caps bytes, and zero uses the MCP message size limit. No contradiction with annotations.

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 brief, front-loads the action, and uses compact bullets. Every sentence earns its place with no redundant or filler content.

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

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a read-only screenshot tool with two parameters and no output schema, the description states the return type, parameter semantics, and default behavior. Nothing essential to invoking the tool correctly is missing.

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

Parameters5/5

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

Schema description coverage is 0%, but the description compensates well for both parameters: area_ui_type maps to the area's ui_type, and size_limit_in_bytes has its cap/default behavior explained. This is exactly the semantic guidance an agent needs beyond the schema enum and integer type.

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?

Opens with a clear verb and resource: 'Take a screenshot of a single Blender area' and specifies the PNG return format. The 'single Blender area' scope distinguishes it from sibling window-screenshot tools such as get_screenshot_of_window_as_image.

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

Usage Guidelines3/5

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

The description implies when to use it (when a screenshot of one Blender area is needed) but does not explicitly state when not to use it or point to an alternative. It could profitably mention that window-level screenshots are served by the sibling window screenshot tools.

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