Skip to main content
Glama

get_screenshot_of_area_as_image

Read-only

Capture a requested Blender area UI type as a PNG image and optionally enforce a byte size limit.

Instructions

Capture the largest editor of the requested Blender area UI type as a PNG.

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 observedv0.8.0

TDQS

B3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds a genuine behavioral detail — that when several editors of the requested type exist, the largest is captured — but omits what happens when no matching area exists, how size_limit_in_bytes is enforced, and whether the image is downscaled or truncated.

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. It is efficient, though the terseness comes at the cost of the parameter and behavioral detail noted elsewhere.

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

Completeness3/5

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

For a two-parameter read-only screenshot tool with no output schema, the description covers the core action adequately. However, with zero schema description coverage and a free-form string parameter that requires specific Blender area identifiers, the definition leaves an agent without enough information to supply a valid argument.

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 carries the burden, yet it only alludes to area_ui_type without listing any valid UI-type strings (e.g. VIEW_3D, PROPERTIES). size_limit_in_bytes is not mentioned at all, and its default of 0 is left ambiguous (unlimited vs. zero bytes).

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?

States a specific verb and resource: capture the largest editor of the requested Blender area UI type, returned as PNG. An agent can tell it produces an image of an area rather than a window, but the description never explicitly contrasts it with 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 Guidelines2/5

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

No guidance on when to choose this over the sibling window-screenshot or JSON screenshot tools, and no prerequisites (e.g. that the area must exist in the current Blender UI). Usage must be inferred from the name and the phrase 'requested area UI type'.

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