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

esp32-iphone-agent

by onehumanbeing
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

press_key

Simulate single keypresses or keyboard shortcuts—such as Enter, Esc, Tab, arrows, Cmd+A, or Shift+Tab—on a real iPhone through an ESP32 USB keyboard.

Instructions

Press a key or combo: enter, esc, tab, backspace, space, up, down, left, right, cmd+a, shift+tab ...

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": {
      "key": "<key>"
    },
    "name": "press_key"
  }
}

Input Schema

NameRequiredDescriptionDefault
keyYes
deviceNoboard id; only needed with several boards

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.5

TDQS

B3.1/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 and falls well short. It discloses the accepted key vocabulary, but says nothing about focus requirements, what happens with an unsupported key, whether combos map to platform modifiers, or what the call returns on success or failure.

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 that leads with the action and follows with the concrete key examples, with no filler. The trailing ellipsis is the only slight cost, but the definition is efficiently sized for a simple two-parameter tool.

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 simple two-parameter tool with no annotations and no output schema, the description covers the key vocabulary but leaves the device parameter's effect and the tool's return/error behavior to inference. It is minimally adequate rather than complete.

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 50%: device already has an inline description, while key is just a bare string. The description partly compensates by listing valid key values (enter, esc, cmd+a, shift+tab), which is real added meaning for the key parameter, but the trailing ellipsis makes the value set ambiguous and non-exhaustive rather than authoritative.

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 (press) and resource (a key or combo) and enumerates concrete examples like enter, esc, tab, cmd+a, shift+tab, which makes the action unambiguous. It does not explicitly distinguish itself from siblings such as type_text or longpress, but the verb/resource pairing is clear enough for an agent to identify the operation.

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?

The description never says when to use this tool versus alternatives like type_text (for strings), tap, or longpress, nor does it mention prerequisites such as focus. Usage is only weakly implied by the enumeration of supported keys, so an agent gets no routing guidance against siblings.

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