frida-ios-mcp

Overview Schema Source Related Servers Discussions Admin

sb_alert_list

List SpringBoard alerts, showing live and raw action view counts, and indicating whether an alert is present.

Instructions

List SpringBoard alerts. Live actionViewCount + actionViewCountRaw (raw may be higher; live can undercount stacks). hasAlert if either count path shows UI. After force: do not trust actionViewCount===1 — use sb_alert_dismiss({all:true}). After dismiss → app screen_snapshot.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "sb_alert_list"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jul 27, 2026

TDQS

A4/5.0

Behavior4/5

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

Despite no annotations, the description explains important behaviors: live count may undercount, raw may be higher, and hasAlert logic based on either count path. It also warns about unreliable state after force operations, which aids safe usage.

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?

The description is three sentences and includes both primary purpose and critical behavioral warnings. It is reasonably concise with no wasted words, though slightly dense.

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?

The description explains output fields (actionViewCount, actionViewCountRaw, hasAlert) and some behavior, but does not fully describe the return format or what constitutes a SpringBoard alert. Given no output schema, more detail could be helpful.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool has no parameters (0 params, schema coverage 100% but empty schema). The description could not add parameter semantics beyond what the schema already conveys, thus baseline 4 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 lists SpringBoard alerts, uses specific verbs ('list'), and distinguishes from sibling tools like sb_alert_trigger, sb_alert_tap, and sb_alert_dismiss by focusing on listing rather than triggering or dismissing.

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 description provides specific guidance after force operations ('do not trust actionViewCount===1 — use sb_alert_dismiss({all:true})') and after dismiss ('take app screen_snapshot'), but lacks broad guidance on when to use this tool versus alternatives or general use cases.

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