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

esp32-iphone-agent

by onehumanbeing
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

longpress

Press and hold at an x,y coordinate to trigger context menus or other touch-and-hold actions on a connected iPhone.

Instructions

Press and hold at x, y.

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": {
      "x": "<x>",
      "y": "<y>"
    },
    "name": "longpress"
  }
}

Input Schema

NameRequiredDescriptionDefault
xYes
yYes
deviceNoboard id; only needed with several boards
duration_msNodefault 1000

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.5

TDQS

C2.7/5.0
Behavior2/5

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

With no annotations, the description carries the full burden and does not meet it: it never states the default hold duration, whether the call blocks until release, what happens at the release point, or any side effects on the target UI. Only the gesture itself is disclosed.

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 front-loaded sentence with no filler. It is efficient, though the brevity is partly the source of the missing information rather than deliberate tightness.

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?

A four-parameter input-mutating UI action with no annotations and no output schema needs at least duration semantics, device targeting, and return/confirmation behavior explained. The description supplies none of these, leaving the agent under-informed.

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 50% (device and duration_ms are described in the schema). The description only echoes x and y and adds no meaning for duration_ms or the multi-board device targeting, so it does not compensate for the gap.

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?

"Press and hold at x, y" states a specific verb (press and hold) and resource (screen coordinates), which implicitly distinguishes it from tap and swipe. It stops short of explicitly naming that sibling distinction, so it does not reach a 5.

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 when-to-use guidance is given: nothing says to prefer this over tap when a long-duration touch is needed, nor when to use press_button/press_key instead. The agent must infer usage purely 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