Skip to main content
Glama
Harusame64

desktop-touch-mcp

by Harusame64
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Local

workspace_snapshot

Get full desktop orientation in one call: display layouts, window thumbnails, and per-window actionable elements with click coordinates. Use after major workspace changes to reset the diff baseline.

Instructions

Purpose: Orient fully in one call — returns display layouts, all window thumbnails (WebP), and per-window actionable element lists with clickAt coords. Details: uiSummary.actionable[] per window includes: action ('click'|'type'|'expand'|'select'), clickAt {x,y} (pass directly to mouse_click), value (current text for editable fields). Runs parallel internally; latency ≈ max(single screenshot), not N×screenshots. Also resets the diffMode buffer so subsequent screenshot(diffMode=true) returns only changes (P-frame). Prefer: Use at session start or after major workspace changes. Use screenshot(detail='meta') for cheap re-orientation within a session. Use screenshot(detail='text', windowTitle=X) for a single-window update. Caveats: Thumbnails are scaled, not 1:1 — use screenshot(dotByDot=true, windowTitle=X) for pixel-accurate coords on a specific window after snapshot. Also: this call resets the screenshot diff baseline (I-frame) and identity tracker as a side effect, so subsequent screenshot(diffMode=true) starts fresh from this snapshot. The reset is not currently exposed in causal/working memory — record an explicit 'workspace_snapshot' step if you need to track the reset point in your causal trail (ADR-010 §11 OQ carry-over for full visibility).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
includeNoOptional response-shape opt-in. `['envelope']` returns the self-documenting envelope (`_version` / `data` / `as_of` / `confidence`). `['raw']` forces raw shape (overrides DESKTOP_TOUCH_ENVELOPE=1 server default). Default behaviour is raw shape (compat with existing clients).
includeUiSummaryNoWhether to include UI element summaries for each window
thumbnailMaxDimensionNoMax size of per-window thumbnail images (default 400px)

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Addedv1.9.2
  2. Removedv1.8.0
  3. Addedv1.6.0
  4. Removedv1.5.1
  5. Addedv1.5.0
  6. Removedv1.4.3
  7. Addedv1.4.2
  8. Removedv1.4.0
  9. Changed1 schema field changedv1.2.1
    • addedInput schema / properties / include
      Added value: +{
+  "description": "Optional response-shape opt-in. `['envelope']` returns the self-documenting envelope (`_version` / `data` / `as_of` / `confidence`). `['raw']` forces raw shape (overrides DESKTOP_TOUCH_ENVELOPE=1 server default). Default behaviour is raw shape (compat with existing clients).",
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}
  10. Addedv1.1.1
  11. Removedv1.1.0
  12. Addedv1.0.3
  13. Removedv0.15.7
  14. Changed5 schema fields changedv0.10.0
    • removedInput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
    • addedInput schema / additionalProperties
      Added value: +false
    • removedInput schema / properties / _stub
      Removed value: -{
-  "description": "Stub tool — arguments ignored."
-}
    • addedInput schema / properties / includeUiSummary
      Added value: +{
+  "default": true,
+  "description": "Whether to include UI element summaries for each window",
+  "type": "boolean"
+}
    • addedInput schema / properties / thumbnailMaxDimension
      Added value: +{
+  "default": 400,
+  "description": "Max size of per-window thumbnail images (default 400px)",
+  "type": "integer"
+}
  15. First observedv0.6.2

TDQS

A4.5/5.0
Behavior5/5

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

With no annotations, the description carries full burden. It discloses internal parallelism ('Runs parallel internally; latency ≈ max(single screenshot)'), side effects ('resets the diffMode buffer', 'resets the identity tracker'), and caveats ('Thumbnails are scaled, not 1:1').

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?

The description is well-structured with sections (Purpose, Details, Prefer, Caveats) and is front-loaded with the key purpose. It is slightly verbose but every sentence adds value; no waste.

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?

Given no output schema, the description explains the return structure (uiSummary.actionable[] with clickAt, value) and behavior (thumbnails as WebP, scaled). It covers side effects and usage context. Minor gap: lacks explicit structure for display layouts.

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 baseline is 3. The description does not add significant meaning beyond the schema; it mentions thumbnailMaxDimension as 'max size' which is already in the schema. The include parameter details are adequately covered in the schema.

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?

The description clearly states the tool's purpose: 'Orient fully in one call — returns display layouts, all window thumbnails (WebP), and per-window actionable element lists with clickAt coords.' It distinguishes from siblings by recommending alternatives like screenshot(detail='meta') for cheap re-orientation.

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

Usage Guidelines5/5

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

The 'Prefer' section explicitly states when to use: 'Use at session start or after major workspace changes.' It also provides alternatives: 'Use screenshot(detail='meta') for cheap re-orientation within a session. Use screenshot(detail='text', windowTitle=X) for a single-window update.'

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Harusame64/desktop-touch-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server