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

fuzzmind-frida-mcp

by fuzzmind
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

frida_ios_url_scheme_hook

Capture incoming URL schemes and Universal Links by hooking UIApplication openURL: and application:openURL:options: on iOS/macOS.

Instructions

[iOS/macOS] Hook URL scheme and Universal Link handling.

Hooks UIApplication openURL:, application:openURL:options:, and application:continueUserActivity:restorationHandler:. Also hooks NSWorkspace openURL: on macOS. Captures incoming URL schemes and Universal Links.

target: process name or pid (string). duration_seconds: how long to capture (default 10).

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": {
      "target": "<target>"
    },
    "name": "frida_ios_url_scheme_hook"
  }
}

Input Schema

NameRequiredDescriptionDefault
targetYes
duration_secondsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior2/5

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

No annotations are provided, so the description must fully disclose behavior. It says 'captures' but does not clarify whether the hook is read-only (monitoring) or modifies behavior (blocking), nor how captured data is retrieved.

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 concise, well-structured with a platform tag, bullet points for parameters, and no unnecessary information.

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?

The description lacks details on output/return value (how captured URLs are accessed) and prerequisites (e.g., attaching to a process). Given no output schema or annotations, more context is needed for complete understanding.

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 description coverage is 0%, but the description adds meaning for both parameters: target is described as 'process name or pid', and duration_seconds as 'how long to capture'. This adds value beyond the schema types.

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 the tool hooks URL scheme and Universal Link handling on iOS/macOS, listing specific APIs. It is unique among siblings, with no overlapping tool for this purpose.

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 implies usage for intercepting URL schemes but does not explicitly state when to use it versus alternatives or provide any 'when not to use' guidance.

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