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

esp32-iphone-agent

by onehumanbeing
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

press_button

Press the HOME hardware button on a connected iPhone to return to the Home Screen. Use it to dismiss apps or menus when automating an iPhone through the ESP32 USB keyboard agent.

Instructions

Press a hardware button. Only HOME (go to the Home Screen).

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": {
      "button": "<button>"
    },
    "name": "press_button"
  }
}

Input Schema

NameRequiredDescriptionDefault
buttonYes
deviceNoboard id; only needed with several boards

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.5

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description must carry the behavioral burden. It usefully discloses that only HOME is supported and what that action does, but says nothing about failure modes (e.g., what happens on other inputs), whether the press is blocking, or what the tool 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?

Two short sentences, front-loaded with the action and followed by the constraint. No wasted wording or filler.

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

Completeness4/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 output schema, the description covers the core constraint that an agent needs to call it correctly. The only gap is the optional device parameter and any return/error behavior, both minor for this complexity level.

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%, and the description reinforces the 'button' parameter by stating only HOME is accepted, matching the enum. The optional 'device' parameter (board id for multi-board setups) is documented only in the schema, so the description adds partial but not full compensation.

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 and resource ('Press a hardware button') and immediately narrows the scope to a single supported value, HOME, with its effect (go to the Home Screen). It doesn't explicitly differentiate itself from siblings like press_key or longpress, but the enum constraint makes the intent unambiguous.

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?

The parenthetical '(go to the Home Screen)' implies the use case, and 'Only HOME' tells the agent there are no other valid options. However, there is no explicit guidance on when to prefer this over press_key or tap, and no mention of which device/environment it applies to.

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