Skip to main content
Glama
Sign In
esp32-iphone-agent

esp32-iphone-agent

by onehumanbeing
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

swipe

Performs a touch drag on a connected iPhone from one screen coordinate to another, ending at the target point so scrollable lists stop there.

Instructions

Swipe from x1, y1 to x2, y2 (rests at the end, so lists stop there).

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": "swipe"
  }
}

Input Schema

NameRequiredDescriptionDefault
x1Yes
x2Yes
y1Yes
y2Yes
deviceNoboard id; only needed with several boards

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.5

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It does disclose a genuinely useful trait — the gesture rests at the end with no momentum, so list scrolling halts at the endpoint — but says nothing about coordinate origin/units, permissions, or what the call returns.

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

Conciseness5/5

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

A single front-loaded sentence with zero filler; the coordinate contract comes first and the behavioral caveat is parenthetical, so nothing is wasted.

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

Completeness3/5

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

For a 5-parameter gesture tool with no annotations, no output schema, and low schema coverage, the definition covers the gesture semantics but leaves coordinate system, optional device behavior, and result/error handling to inference.

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 only 20% (just the 'device' field), so the description must compensate. Mapping x1,y1 and x2,y2 to start and end points of the swipe does add meaning beyond bare 'number' types, but units, screen coordinate space, and the device-selection condition remain undocumented.

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 exact resource of the gesture: the two endpoint coordinate pairs. An agent can distinguish it from tap or longpress by the coordinate-pair structure, though no sibling is named explicitly.

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

Usage Guidelines3/5

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

Usage is only implied: the note that lists 'stop there' hints this is the tool for scrolling/dragging, but there is no explicit when-to-use versus tap/longpress or when a different gesture is preferable.

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