Skip to main content
Glama
mobile-next

Mobile Next MCP Server

Official
by mobile-next
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Swipe Screen

mobile_swipe_on_screen

Perform a swipe gesture on a mobile device screen by specifying direction, starting coordinates, and distance.

Instructions

Swipe on the screen

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
xNoThe x coordinate to start the swipe from, in pixels. If not provided, uses center of screen
yNoThe y coordinate to start the swipe from, in pixels. If not provided, uses 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. Changed2 schema fields changedv1.0.3
    • addedInput schema / properties / x / minimum
      Added value: +0
    • addedInput schema / properties / y / minimum
      Added value: +0
  2. Addedv1.0.0

TDQS

C2.7/5.0
Behavior2/5

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

The annotations (readOnlyHint=false, destructiveHint=false) already indicate a non-read-only, non-destructive action. The description adds no behavioral context such as potential side effects on UI elements, scrolling behavior, or failure conditions. It does not contradict annotations but adds no extra transparency.

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 sentence, but it is under-specified rather than concise. It repeats the tool name without adding useful content, so it does not 'earn its place' as a meaningful elaboration. It is more of a placeholder than a well-structured definition.

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 tool with 5 parameters and no output schema, the description is highly incomplete. It lacks information about return values, side effects, or interaction with the UI. Annotations cover basic safety but not the operational context needed for reliable use.

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 each parameter (x, y, device, distance, direction) is already documented. The description itself adds no parameter-related information. Per the rubric, a high schema coverage sets a baseline of 3, which is appropriate here.

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 'Swipe on the screen' clearly indicates a swipe gesture on the mobile screen, matching the tool name and title. It is specific enough to distinguish from other touch actions like click or long press by name, but the description itself does not add any differentiation detail beyond the resource and verb.

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 on when to use this tool versus alternatives such as click, double tap, or long press. No context about typical use cases, prerequisites, or exclusions is provided, leaving the agent to infer usage solely from the name.

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