Skip to main content
Glama

ios_key

Simulate hardware button presses on unjailbroken iOS/iPadOS devices to trigger Home, Volume Up, or Volume Down actions through MCP.

Instructions

Press hardware button: HOME, VOLUME_UP, or VOLUME_DOWN.

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_name": "<key_name>"
    },
    "name": "ios_key"
  }
}

Input Schema

NameRequiredDescriptionDefault
key_nameYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

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 burden. It doesn't say what each key does on the device (e.g., HOME returns to the home screen, volume keys alter device volume), whether the press is a single tap or hold, or whether any permissions/state are required. For a state-mutating device action with zero annotation coverage, this is thin.

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?

One front-loaded sentence that names the action and its accepted values with no filler. Every word earns its place.

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?

An output schema exists, so return values needn't be explained. Still, with no annotations and no parameter documentation in the schema, the definition leaves gaps around key behavior and when to prefer this over tap-based siblings.

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 0%, so the description must compensate — and it does partially by naming the three valid key values, which the schema leaves as an unconstrained string. However, it never ties those values to the key_name parameter, nor states case sensitivity or the expected string format.

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 (hardware button) and enumerates the three supported keys, which makes the tool's scope concrete. It does not explicitly contrast itself with siblings like ios_tap, but the hardware-key framing is specific enough to be distinguishable.

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?

There is no guidance on when to use this rather than ios_tap or ios_swipe, and no prerequisites or platform constraints are mentioned. The agent must infer that this is for physical device buttons only.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.