Skip to main content
Glama
Sign In
re-ios

re-ios

by gyh20062008-commits
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

decrypt_ipa

Decrypt FairPlay DRM from iOS apps and dump decrypted IPA using frida-ios-dump. Requires tethered iOS device with Frida.

Instructions

Decrypt FairPlay DRM from an iOS app using frida-ios-dump.

Dumps decrypted IPA from a running/installed app on a tethered iOS device. Requires frida-ios-dump to be installed.

Args: bundle_id: Bundle identifier of the target app output_dir: Output directory for decrypted IPA (default: /tmp/ios_decrypted) device_type: Device type: 'usb', 'local', or 'remote' (default: 'usb') device_id: Specific device ID (optional)

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": {
      "bundle_id": "<bundle_id>"
    },
    "name": "decrypt_ipa"
  }
}

Input Schema

NameRequiredDescriptionDefault
bundle_idYes
device_idNo
output_dirNo/tmp/ios_decrypted
device_typeNousb

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.1

TDQS

A3.8/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 mentions requirement and output, but doesn't disclose side effects, error conditions, or reversibility.

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?

Two clear sentences of purpose followed by a requirements note and bullet-point parameters. Well-structured and appropriately sized, though could be slightly tighter.

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?

Lacks information about return values or output format. Given no output schema and 4 params, the description covers purpose and parameters but omits result communication details.

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?

Input schema has 0% coverage but description includes an Args section that explains each parameter's purpose and defaults, adding meaningful context beyond schema titles.

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 decrypts FairPlay DRM from iOS apps using frida-ios-dump, distinguishing it from sibling tools that perform analysis, resigning, or other operations.

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?

Implies usage for encrypted IPAs on tethered devices with frida-ios-dump installed, but lacks explicit 'when-not-to-use' or comparisons with alternatives among siblings.

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