Skip to main content
Glama

screenshot

Read-onlyIdempotent

Capture a PNG image of the current Excalidraw canvas and editor toolbar without bringing the window into focus.

Instructions

Return a PNG image of the current canvas and editor toolbar without focusing its window.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered structurally. The description adds the one behavioral trait annotations cannot express — that the capture does not focus or steal the target window — which is genuinely useful for deciding when to call it. It stops short of describing image resolution, size, or what happens with occluded/minimized windows.

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?

A single short sentence with the resource stated first and the non-focusing constraint trailing. No filler, no restatement of the tool name.

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?

With no parameters, no output schema, and rich annotations, the description needs only to convey what is produced and any side effects — and it does both by naming the PNG return and the no-focus behavior. Remaining gaps (image dimensions, behavior for hidden/minimized windows) are minor for a zero-argument capture tool.

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 and the schema is empty at 100% coverage, so there is nothing for the description to disambiguate. The baseline of 4 applies; no param-level meaning is missing.

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?

The description gives a specific verb (return) and resource (a PNG image of the current canvas and editor toolbar), plus a scoping qualifier ('without focusing its window'). 'PNG' implicitly contrasts with the SVG-oriented sibling export_svg, but it never names that alternative, so sibling differentiation is left to inference.

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 only implied: the word 'current' signals a snapshot of live state, and 'without focusing its window' hints at a non-intrusive capture use case. There is no explicit when-to-use or when-not-to-use statement and no routing to export_svg or read_scene for non-image needs.

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