Skip to main content
Glama
Sign In
frida-ios-mcp

frida-ios-mcp

by YPYT1
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript

sb_alert_trigger

Create a test system alert on iOS. Optionally force stacking multiple alerts for testing alert management workflows.

Instructions

[advanced] Create a test system alert (SBAlertItemTestRecipe). Default force=false: skip if alert already present (no stack). force:true stacks another. Next: sb_alert_list → sb_alert_dismiss({all:true}) or sb_alert_tap.

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_trigger"
  }
}

Input Schema

NameRequiredDescriptionDefault
forceNoDefault false — do not stack if actionViews/alerts already exist

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.4/5.0
Behavior4/5

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

No annotations provided, so description carries full burden. Describes default behavior (skip if alert present) and force parameter (stack another), which is good, but lacks details on permissions or side effects.

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?

Extremely concise: two sentences with front-loaded purpose, minimal wasted words. Efficiently communicates key info.

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 tool with one parameter and no output schema, the description covers purpose, parameter behavior, and next steps. Lacks failure scenarios but is adequate.

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?

Schema has 100% coverage for the single parameter, but description adds nuance (e.g., 'no stack' vs 'stacks another') beyond the schema's 'do not stack', improving agent understanding.

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?

Clearly states it creates a test system alert (SBAlertItemTestRecipe), distinguishing it from siblings like sb_alert_list (list), sb_alert_dismiss (dismiss), and sb_alert_tap (tap). The '[advanced]' label adds context.

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?

Implies usage via sibling differentiation and explicit next steps (sb_alert_list → sb_alert_dismiss or sb_alert_tap), but lacks explicit when-not-to-use or alternative conditions.

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