Skip to main content
Glama

desktop_wait

Read-onlyIdempotent

Wait until the screen of a desktop session changes since your last screenshot (or until the timeout), then let it settle briefly — e.g. after starting an app. Take a screenshot afterwards. 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_wait"
  }
}

Input Schema

NameRequiredDescriptionDefault
session_idYesDesktop session id from desktop_list
timeout_msNoAt most 10000 (default 3000)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive behavior. The description adds useful context beyond them: it waits for a change since the last screenshot or times out, lets the screen settle briefly, notes that the user can watch the session, and warns against entering secrets. It still does not spell out the exact result on timeout, so it is not fully exhaustive.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The core behavior is front-loaded and easy to find, but later sentences about screenshot coordinates and never typing passwords are family-level or general safety guidance rather than specifics of waiting. Those sentences dilute focus even though the description remains readable.

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?

For a simple wait operation with full parameter documentation and annotations covering safety, the definition supplies the needed context: trigger condition, settle behavior, follow-up screenshot, and session ownership. The main omission is a clear statement of what the call returns on change versus timeout, which is minor without an output schema.

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%, and the schema itself documents session_id as coming from desktop_list and timeout_ms with its maximum and default. The description mentions timeout and last-screenshot context, but adds no new syntax or format details for either parameter, so the baseline of 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?

The first sentence states a specific verb and resource: waiting for a desktop session's screen to change, with a timeout alternative. The purpose is clear, but it only implicitly distinguishes itself from desktop_screenshot by saying to take a screenshot afterwards, without naming the sibling tool.

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?

It gives a concrete use case, 'e.g. after starting an app,' and a follow-up action, 'Take a screenshot afterwards,' which tells the agent when this tool fits. It does not state when not to use it or explicitly name alternative tools.

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.