Skip to main content
Glama
khoa-le

mobile-mcp

by khoa-le
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Hybrid

Swipe Screen

mobile_swipe_on_screen

Swipe a mobile device screen in a chosen direction to scroll or navigate. Set optional start coordinates and distance for precise control.

Instructions

Swipe on the screen

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
xNoThe x coordinate to start the swipe from, in pixels. Give both x and y, or neither to start from the center of screen
yNoThe y coordinate to start the swipe from, in pixels. Give both x and y, or neither to start from the center of screen
deviceYesThe device identifier to use. Use mobile_list_available_devices to find which devices are available to you.
distanceNoThe distance to swipe in pixels. Defaults to 400 pixels for iOS or 30% of screen dimension for Android
directionYesThe direction to swipe

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.0.1

TDQS

C2.2/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=false, openWorldHint=true, and destructiveHint=false, so the safety profile is known. The description adds no behavioral context beyond those annotations, such as what the swipe affects, whether it scrolls or navigates, or any side effects.

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

Conciseness2/5

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

The description is a single short phrase with no wasted words, but it is under-specified rather than concise. Like the calibration example 'Process', its brevity reflects missing substance, not efficient communication.

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?

Even with rich schema coverage and safety annotations, the description does not help an agent understand when this gesture is appropriate or how it relates to adjacent gesture tools. For a swipe tool with five parameters and multiple sibling gesture tools, more contextual framing is needed.

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%, with each parameter including a description, so the schema fully documents required device and direction plus optional x, y, and distance. The description adds no parameter meaning, so the baseline score of 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Swipe on the screen' is a near-exact restatement of the tool name and title, fitting the rubric's tautology category. It states a verb and resource but does not differentiate the tool from sibling gestures such as click, double-tap, or long-press.

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 guidance about when to use swipe versus alternatives like click_on_screen or press_button, and no prerequisites are mentioned. The description merely repeats the operation without any context for selection.

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