frida-ios-mcp

by YPYT1

Overview Schema Source Related Servers Discussions Admin

JavaScript

device_list

List connected Frida devices, defaulting to USB-only. Requires matching frida-server on the iOS device.

Instructions

List Frida devices. Default USB-only. Need matching frida-server on phone (17.x with this package).

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": "device_list"
  }
}

Input Schema

Name	Required	Description	Default
`usbOnly`	No	Default true: only USB devices. Set false to include local/socket.

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 provided, so description carries full burden. It discloses default behavior and a prerequisite, but lacks details on error cases or return format.

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?

Two efficient sentences, front-loaded with purpose, no wasted words.

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 list tool with few parameters, the description covers purpose, default, and prerequisite. Missing error handling details, but adequate for low complexity.

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 100% and already describes the only parameter. Description adds the prerequisite about frida-server but not significant additional parameter context beyond 'default USB-only'.

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 the tool lists Frida devices and defaults to USB-only. No sibling tool does the same thing, so it distinguishes itself well.

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?

States prerequisite (frida-server) and default mode, which guides when to use. Does not explicitly state when not to use, but context is clear.

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