Skip to main content
Glama

desktop_watch_read

Read the latest observation of a live desktop session to get recognized screen text, its timestamp, and whether the screen changed since a given point.

Instructions

Read the latest observation of a live desktop session.

Returns the recognised screen text (bounded), when it was observed, whether it changed since since, and how many frames were skipped as unchanged.

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

Input Schema

NameRequiredDescriptionDefault
sinceNo
as_imageNo
session_idNo

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?

No annotations exist, so the description carries the full burden. It usefully discloses the return shape (bounded recognised text, observation timestamp, change flag, skipped-frame count), which is real behavioral value, but it says nothing about permissions, what happens if no session exists, or how `as_image` changes the response.

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?

Two sentences, front-loaded with the purpose, followed by a precise enumeration of returned fields. Nothing is wasted and the return information is the useful part.

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

Completeness2/5

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

There is no output schema and no annotations, and two of three parameters are wholly undefined in both schema and description. Combined with no statement of preconditions (active watch session) or behavior on the image path, the definition leaves an agent guessing on key inputs.

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

Parameters2/5

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

Schema description coverage is 0% across three parameters. The description adds meaning for `since` only implicitly ('whether it changed since `since`'), and gives no explanation of `as_image` (does it return a screenshot instead of text?) or `session_id` (which session, and what the empty default means).

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: 'Read the latest observation of a live desktop session.' It is clearly distinguishable from mutating siblings like desktop_click and desktop_type, but it never names or contrasts with near-neighbors such as desktop_read_value or eyes_see_desktop, so sibling differentiation is only implicit.

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 by the phrase 'live desktop session' and by the `since` comparison; there is no explicit statement about when to prefer this over desktop_read_value or eyes_see_desktop, nor any stated prerequisite (e.g. that a watch must be started first via desktop_watch_start).

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