Skip to main content
Glama
Sign In
twiddle-mcp

twiddle-mcp

by roti-c137
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

swipe

Perform swipe gestures on mobile emulators or simulators, either in a direction or between specified coordinates.

Instructions

Swipe in a direction (from screen center) or between explicit points.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "swipe"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNo
fromNo
deviceNoDevice id from list_devices. Optional when exactly one device is booted.
directionNo
durationMsNoDefault 300

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.2

TDQS

C2.4/5.0
Behavior1/5

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

No annotations are provided, and the description does not disclose behavioral traits like mutability, waiting behavior, or error handling. It merely states the action without any safety or side-effect information.

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?

Single sentence, efficient and front-loaded. However, it could benefit from a brief breakdown of the two modes for clarity.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Despite having 5 parameters including nested objects, no output schema, and no annotations, the description is too sparse. It omits details like coordinate system, duration units, and default behavior of 'from' when using 'direction'.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 40%, and the description adds little to parameter understanding. The 'direction' and 'from'/'to' parameters are not explained beyond their names; the default origin when using 'direction' is implied but not explicit.

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 clearly states it performs a swipe action and identifies two modes: from screen center via direction, or between explicit points. This distinguishes it from sibling tools like tap (single point) and type_text (text input).

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?

No guidance on when to use swipe versus alternatives like tap or press_button. Prerequisites, such as device boot status or validity of coordinates, are not mentioned.

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