re-ios

full_analysis

Run comprehensive analysis on iOS targets: extract metadata, perform static analysis of binaries, and enable dynamic Frida hooks. Supports IPA, Mach-O, and bundle IDs with adjustable analysis levels.

Instructions

Run a comprehensive analysis pipeline on an iOS target.

Supports three levels:

'basic': IPA metadata only
'static': Full static analysis (IPA + Mach-O + ObjC + Swift + encryption)
'dynamic': Static analysis + Frida runtime hooks (requires device)

Args: target: Path to IPA file, Mach-O binary, or bundle ID for dynamic analysis level: Analysis level: 'basic', 'static', or 'dynamic' (default: 'static') output_dir: Output directory for analysis artifacts (default: /tmp/re_ios_analysis)

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

Input Schema

Name	Required	Default
`level`	No	static
`target`	Yes
`output_dir`	No	/tmp/re_ios_analysis

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.1Jul 9, 2026

TDQS

A3.6/5.0

Behavior2/5

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

No annotations are provided, and the description does not disclose whether the tool is read-only, modifies the target, or has side effects. The mention of dynamic hooks implies potential runtime interactions, but safety implications are not addressed.

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 front-loaded with the main purpose, followed by a concise bullet list of levels. It is efficient and well-structured, though the parameter details could be more compact.

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 covers the different analysis levels and parameters, but lacks information on the output format, return value, or how the agent can use the results. Given the complexity, more detail on artifacts would improve completeness.

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?

With 0% schema description coverage, the description fully explains all three parameters: target as path or bundle ID, level with explicit allowed values and default, and output_dir with default path. This adds meaning beyond the bare schema.

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 runs a 'comprehensive analysis pipeline' on an 'iOS target' and enumerates three specific analysis levels, distinguishing it from sibling tools that focus on individual aspects.

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 explains the three levels and notes that dynamic requires a device, but does not explicitly advise when to use this tool versus sibling tools like analyze_macho_archs or full_static_analysis.

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