Skip to main content
Glama

get_screenshot_of_window_as_image

Read-only

Captures the active Blender window as a PNG image, with an optional byte limit to control file size.

Instructions

Capture the active Blender window as a PNG, with an optional byte limit.

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

Input Schema

NameRequiredDescriptionDefault
size_limit_in_bytesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.8.0

TDQS

A3.5/5.0
Behavior3/5

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

The definition is consistent with readOnlyHint=true and openWorldHint=false, and it adds the PNG format plus the existence of a byte cap, which is useful. It does not say what happens when the limit is hit (truncate, downscale, or error) or anything about how the image is returned, so the behavioral picture is only partly filled in.

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?

One short sentence with the resource and format front-loaded and zero filler; nothing could be trimmed without losing content.

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 simple one-parameter read tool with no output schema, the definition is adequate but leaves the return payload and size-limit behavior undefined, which matters because the whole point of the tool is the returned image.

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 0% for the single parameter, so the description must carry the load. 'Optional byte limit' adds the notion that it is not required and caps output size, but it doesn't explain the semantics of the default 0 (presumably no limit) or what occurs when the cap is exceeded.

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 ('Capture') and resource ('active Blender window') plus the output format (PNG), which distinguishes it from get_screenshot_of_area_as_image. It stops short of explicitly contrasting itself with get_screenshot_of_window_as_json, but the format marker does most of that work.

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?

Usage is implied by 'active Blender window' (as opposed to an arbitrary area), but there is no explicit statement of when to prefer this over the area or JSON screenshot siblings, and no preconditions are given.

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