Skip to main content
Glama

get_screenshot_of_window_as_json

Read-only

Capture the active Blender window as JSON, including editor layout and selection, to inspect scenes or document workspaces.

Instructions

Describe the active Blender window, editor layout and selection.

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_json"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.8.0

TDQS

B3.1/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 and the description carries a lighter burden. The description adds nothing beyond that, though: it does not say whether the call depends on window focus, whether it captures state at call time, or how large/expensive the result is. An output schema exists, so return-shape disclosure is not required.

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, but the brevity comes at the cost of the one distinction that matters most (JSON description vs image capture), so it is tight rather than fully earned.

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 zero-parameter read-only tool with an output schema and clear annotations, most structural information is already supplied, so the description is nearly adequate. The remaining gap is the pivotal one: nothing explains what this returns relative to its image-producing siblings, which is exactly the information an agent needs to select it correctly.

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

Parameters4/5

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

The tool takes zero parameters, so there is nothing for the description to disambiguate; the baseline of 4 applies. The description does not introduce any phantom parameters, which is consistent with the empty schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description gives a verb ("Describe") and a target ("the active Blender window, editor layout and selection"), which is concrete enough to know it returns a textual/structured description rather than pixels. However, it never resolves the ambiguity implicit in the name and in the sibling get_screenshot_of_window_as_image: an agent cannot tell from the description whether this captures an image or returns JSON metadata, nor what distinguishes it from the image variant.

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?

There is no guidance on when to choose this over get_screenshot_of_window_as_image or get_screenshot_of_area_as_image, despite those being the obvious alternatives. No preconditions are stated (e.g., that a window must be active/focused). Usage must be inferred entirely from the tool name.

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