frida-ios-mcp

by YPYT1

Overview Schema Source Related Servers Discussions Admin

JavaScript

sb_alert_tap

Tap a SpringBoard alert button by matching its title and capture a screen snapshot.

Instructions

[advanced] Tap SpringBoard alert button by title. Then call app screen_snapshot. Do not parallel with dismiss.

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": {
      "title": "<title>"
    },
    "name": "sb_alert_tap"
  }
}

Input Schema

Name	Required	Description	Default
`title`	Yes	Button title to match

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jul 27, 2026

TDQS

A4/5.0

Behavior3/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 discloses that it's an advanced action and gives after-use instructions. However, it does not detail side effects, error behavior (e.g., if button not found), or whether it requires specific app state. This is adequate but could be more transparent.

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?

The description is extremely concise, consisting of three short sentences. Each sentence adds unique information: the action, a required follow-up, and a parallelism constraint. No unnecessary words or repetition.

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?

Given the tool has one parameter and no output schema, the description covers the core action and provides important context (post-action and parallelism rule). It does not explain error handling or what happens if the title does not match, but for a simple tap action, this is largely sufficient.

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 description coverage is 100% with the schema describing 'title' as 'Button title to match'. The description adds 'by title', which is redundant. No additional semantic meaning beyond the schema is provided, so baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states it taps a SpringBoard alert button by title. 'Tap SpringBoard alert button' is a specific verb-resource pair. It distinguishes from sibling tools like sb_alert_dismiss and sb_alert_trigger, which perform different actions on alerts.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides guidance: call screen_snapshot after tapping, and do not parallel with dismiss. However, it does not explicitly state when to use this tool versus alternatives like sb_alert_dismiss or sb_alert_list. The context is implied but not fully differentiated.

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