Skip to main content
Glama
Sign In
gwagent

gwagent

by vcnngr
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

ui_swipe

Simulates a raw swipe gesture between two screen coordinates on an Android device or emulator, with optional duration control.

Instructions

Raw swipe gesture between two points.

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": {
      "x1": "<x1>",
      "y1": "<y1>",
      "x2": "<x2>",
      "y2": "<y2>"
    },
    "name": "ui_swipe"
  }
}

Input Schema

NameRequiredDescriptionDefault
x1YesStart X.
x2YesEnd X.
y1YesStart Y.
y2YesEnd Y.
duration_msNoGesture duration.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.8/5.0
Behavior2/5

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

With no annotations, the description carries the full burden and discloses almost nothing beyond the gesture existing — not whether it blocks, whether it changes UI state, how duration affects the swipe, or whether the device must be unlocked. 'Raw' hints that no path smoothing or targeting is applied, which is a small piece of the picture.

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?

It is a single front-loaded sentence with no waste, but the terseness shades into under-specification rather than genuine economy — one more clause on coordinate space or the ui_scroll alternative would have cost little.

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?

For a 5-parameter device-input primitive with no annotations and no output schema, the description omits the essentials an agent needs: coordinate reference frame, whether duration changes gesture velocity, blocking behaviour, and required device state.

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 the schema already documents all five parameters, and the description adds no coordinate-space, unit, or duration semantics beyond what is there. Baseline 3 applies when the schema does the heavy lifting.

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 description states a specific verb and resource: a 'swipe gesture between two points', with 'raw' signalling a low-level primitive. It is clear what the tool performs, but it never names ui_scroll or ui_tap to say how it differs from the higher-level gesture siblings.

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

Usage Guidelines2/5

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

There is no statement of when to reach for this instead of ui_scroll, ui_tap or ui_double_tap, and no preconditions (foreground app, device connected). The word 'raw' weakly implies 'use when you need exact coordinates', but nothing is explicit.

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