Skip to main content
Glama
fixed-width

glass

by fixed-width
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Rust

glass_gesture

Execute multi-touch gestures (pinch, rotate, swipe) using 2–10 pointers with window-relative start/end points and duration. Returns a clear error when the backend lacks multi-touch support.

Instructions

Perform a multi-touch gesture: 2–10 pointers, each a straight from→to segment in window-relative px, all down together at t=0 and up at duration_ms. Pinch = two pointers toward/apart; rotate = two on an arc; two-finger swipe = two parallel segments; a from==to pointer is held. Multi-touch isn't available on every backend — it returns a clear Unsupported error where the active backend can't do it.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pointersYes2–10 simultaneous pointers; each a straight from→to segment. Pinch = two pointers moving toward/apart; rotate = two on an arc; two-finger swipe = two parallel segments.
duration_msNoSpan the gesture over this many ms (all pointers down at 0, up at duration). Default 250.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.8.0
    • changedInput schema / $defs / PointArg / properties / x / description
      Previous value: -"Window-relative x — 0 is the window's left edge, not the screen's."New value: +"Window-relative x in pixels."
    • changedInput schema / $defs / PointArg / properties / y / description
      Previous value: -"Window-relative y — 0 is the window's top edge, not the screen's."New value: +"Window-relative y in pixels."
  2. Changed3 schema fields changedv1.2.0
    • addedInput schema / $defs / PointArg / properties / x / description
      Added value: +"Window-relative x — 0 is the window's left edge, not the screen's."
    • addedInput schema / $defs / PointArg / properties / y / description
      Added value: +"Window-relative y — 0 is the window's top edge, not the screen's."
    • removedInput schema / title
      Removed value: -"GestureArgs"
  3. Addedv1.0.2

TDQS

A4.5/5.0
Behavior5/5

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

Beyond the annotations (readOnlyHint=false, destructiveHint=false, openWorldHint=false), the description reveals important behavioral traits: all pointers go down simultaneously at t=0 and up at duration_ms, a from==to pointer is held, and multi-touch may return an Unsupported error depending on backend. No contradiction with annotations.

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?

The description is information-dense with no wasted words. It front-loads the core purpose ('multi-touch gesture'), packs constraints into the first sentence, and uses the second sentence for examples and a backend caveat. Every clause earns its place.

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?

For a tool with no output schema and only two parameters, the description covers what an agent needs: the gesture model, pointer count range, timing behavior, held-pointer semantics, and the backend limitation. Together with the fully described schema, this is sufficient for correct invocation.

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 the schema already documents the pointers array and duration_ms. The description adds value by describing gesture patterns (pinch, rotate, swipe) and clarifying that all pointers are synchronized, but most parameter meaning is already present in the schema, so the additional contribution is moderate.

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 states a specific verb ('Perform') and resource ('multi-touch gesture') with precise scope: 2–10 pointers, each a straight from→to segment in window-relative px, all down together at t=0 and up at duration_ms. This clearly differentiates it from single-pointer siblings like glass_drag, glass_click, and glass_scroll.

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?

The description gives concrete use cases: pinch, rotate, two-finger swipe, and held pointers. It clearly implies this tool is for multi-touch gestures rather than simple single-pointer interactions, though it does not explicitly name when-not-to-use it or point to specific sibling tools for single-pointer alternatives.

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

Deploy Server

Other Tools