Skip to main content
Glama

desktop_screenshot

Read-onlyIdempotent

Take a screenshot of a desktop session (JPEG). Returns the picture and its size; the coordinates of the other desktop tools are pixels of the last screenshot. Take a new one after acting to see the result. The user started this desktop session for you in Termalin and can watch it. Coordinates are pixels of your last desktop_screenshot. Never type passwords, keys or other secrets: when a sign-in or secret is needed, stop and ask the user to type it themselves.

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": {
      "session_id": "<session_id>"
    },
    "name": "desktop_screenshot"
  }
}

Input Schema

NameRequiredDescriptionDefault
max_edgeNoLongest side of the picture in pixels (320–1920, default 1280)
session_idYesDesktop session id from desktop_list

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior5/5

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

Beyond the annotations (readOnly, idempotent, non-destructive, open-world), the description discloses that the picture and its size are returned, that coordinates used by sibling tools are in the pixel space of the most recent screenshot, that the session is user-visible and was started in Termalin, and a hard safety rule about secrets. This covers the meaningful behavioral profile the annotations cannot express.

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?

Front-loaded with the action and its return value, and every sentence carries operational information. The coordinate-scoping rule is stated twice ('the coordinates of the other desktop tools are pixels of the last screenshot' and 'Coordinates are pixels of your last desktop_screenshot'), which is redundant but not harmful.

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

Completeness5/5

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

With no output schema, the description still explains what is returned (the picture and its size). It also covers the session-provenance and user-visibility context and the secrets policy, so an agent has everything needed to call it correctly and safely in the desktop loop.

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 100%, so both parameters (session_id and max_edge with its 320–1920 range) are already documented in the schema. The description adds only indirect meaning, clarifying that coordinates are in the pixel space of the last screenshot, which matters for how max_edge resizing interacts with subsequent actions. Baseline 3 is appropriate.

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

Purpose5/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 screenshot of a desktop session') plus the output format (JPEG), and implicitly positions itself as the observation step against the acting tools (click/key/type/move) whose coordinates it defines. An agent can tell exactly what this tool produces without opening the schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

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

Gives concrete when-to-use guidance: 'Take a new one after acting to see the result', and warns to stop and ask the user when a sign-in or secret is involved. It does not name explicit alternatives or when-not conditions, but for a screenshot tool the usage context is clear.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.