Skip to main content
Glama
Sign In
ios-agent-driver

ios-agent-driver

by CodeJonesW
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

press_button

Press hardware buttons (HOME, LOCK, SIDE_BUTTON, SIRI, APPLE_PAY) on an iOS Simulator to trigger system actions like backgrounding the app or locking the screen.

Instructions

Press a hardware button (HOME backgrounds the app; LOCK locks the 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
udidNoTarget simulator UDID. Defaults to the booted sim.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/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. It explains effects for HOME and LOCK but omits behavior for SIDE_BUTTON, SIRI, and APPLE_PAY. No mention of whether these actions are reversible or require special permissions.

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 sentence that is concise and front-loaded. However, it could be expanded to cover all button options without becoming overly verbose.

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?

Given the tool has 5 enum values and no output schema or annotations, the description is incomplete. It only partially explains effects and lacks details on return values or side effects.

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% (only udid described). The description adds meaning for two button enum values (HOME and LOCK) but not the other three. It provides some value beyond the schema but does not fully compensate.

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?

The description clearly states the tool presses a hardware button and gives specific examples for HOME and LOCK. While it doesn't explicitly distinguish from sibling tools like tap or swipe, the verb 'press' and reference to 'hardware button' make the purpose reasonably clear.

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 this tool versus alternatives like tap or deeplink. No mention of prerequisites or context, leaving the agent to infer usage.

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