Skip to main content
Glama

desktop_screenshot

Capture a PNG screenshot of a specific app window or display to inspect desktop UI, saving to file or returning base64.

Instructions

agent-desktop screenshot: Take a PNG screenshot of an application 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": "desktop_screenshot"
  }
}

Input Schema

NameRequiredDescriptionDefault
appNoFilter to application by name
screenNoCapture display by index (from list-displays; 0 = primary)
window_idNoScope to a single window ID (from list-windows)
output_pathNoSave to file instead of returning base64

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It does disclose the two output modes — base64 by default versus writing to a file via output_path — which is genuine behavioral value, but it omits what happens with zero filters (all displays? whole screen?), how multi-window matches are resolved, and whether the capture has side effects or permission requirements.

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 that states capability and output format with no wasted wording. The 'agent-desktop screenshot:' prefix partially restates the tool name, a minor redundancy.

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?

There is no output schema, so the description rightly mentions the return medium (base64 vs saved file). However, for a tool where all parameters are optional, the description never states the default capture scope when no filters are given, which is the most likely agent confusion.

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 description coverage is 100%, so all four parameters are already documented in the schema (app filter, display index, window ID, file output). The description adds no additional semantics such as precedence when app, screen, and window_id are combined, so the baseline 3 applies.

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 ('Take a PNG screenshot of an application window') and fixes the output format as PNG, so the agent knows exactly what the tool produces. It does not distinguish itself from siblings such as desktop_list_windows or desktop_get, which the description would need to mention for a 5.

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 explicit when-to-use guidance, no when-not-to-use, and no named alternatives among the many desktop_* siblings. The only usage hint is implicit in the filter parameters (app/screen/window_id), which an agent must interpret on its own.

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