Skip to main content
Glama
Sign In
orion-phone-mcp

orion-phone-mcp

by OrionArchitekton
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

swipe

Simulate a finger drag on a leased Android emulator, moving from start coordinates to end coordinates over a specified millisecond duration.

Instructions

Swipe from one point to another over ms milliseconds (1 to 10000).

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

Input Schema

NameRequiredDescriptionDefault
msNo
x1Yes
x2Yes
y1Yes
y2Yes
phoneYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

C2.7/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. It usefully discloses the duration range (1 to 10000 ms, a constraint absent from the schema), but says nothing about which device is targeted, whether coordinates are absolute or relative, or any side effects on UI state.

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?

A single short sentence with no waste, and the essential gesture semantics are front-loaded. It is terse rather than padded, though it errs toward under-specification.

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 6-parameter automation tool with no annotations and 0% schema coverage, the description is inadequate: it never explains the coordinate system, the required phone target, or how a swipe differs operationally from other gesture tools. An output schema exists, so return values need not be covered.

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 description coverage is 0%, so the description must compensate, yet it only adds a range for ms. The five required parameters (phone, x1, y1, x2, y2) remain completely unmapped to any meaning, coordinate space, or units.

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?

States a specific verb (swipe) and the action's shape: a gesture from one point to another over a duration. This is distinguishable from sibling gestures like tap, type, and key, which perform different input actions.

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 tap or other input tools, and no mention of prerequisites (e.g. an active phone session via lease). The agent must infer usage entirely from the name and sibling list.

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