Skip to main content
Glama

ios_binary_strings

Extracts printable strings from an iOS app binary and filters for security-relevant URLs, API keys, credentials, emails, and private IPs.

Instructions

Extracts printable strings from an iOS app binary and filters for security-relevant patterns: HTTP/S URLs, API keys, AWS/Firebase/Google credentials, email addresses, and private IP addresses.

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": {
      "ipa_path": "<ipa_path>"
    },
    "name": "ios_binary_strings"
  }
}

Input Schema

NameRequiredDescriptionDefault
filterNoFilter output: all | url (HTTP endpoints) | key (API key patterns) | email | ip (private IPs)all
ipa_pathYesAbsolute path to the IPA file to analyze
min_lengthNoMinimum string length to include (default 8 — shared with the secret scanners)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.3.0
    • changedInput schema / properties / min_length / default
      Previous value: -6New value: +8
    • changedInput schema / properties / min_length / description
      Previous value: -"Minimum string length to include (default 6)"New value: +"Minimum string length to include (default 8 — shared with the secret scanners)"
  2. First observedv1.1.1

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full behavioral burden. It discloses the scan targets and implies a read-only extraction, but says nothing about output shape, behavior on encrypted binaries, size/perf limits, or whether findings are deduplicated or grouped.

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?

A single front-loaded sentence that names the action first and enumerates the pattern categories second. Every clause carries information and there is no filler.

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 three-parameter, fully schema-documented extraction tool with no output schema, the description covers what is scanned and the filterable categories adequately. The main remaining gap is return-value shape and handling of non-plaintext binaries, which is a moderate rather than severe omission given the tool's simplicity.

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%, so all three parameters are already documented, making 3 the baseline. The description does add a small amount of meaning by expanding the "key" filter into AWS/Firebase/Google credential categories, but it says nothing about min_length semantics or the interaction between filters.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a concrete verb and resource ("Extracts printable strings from an iOS app binary") and then specifies the pattern categories found. An agent knows exactly what it produces, though nothing distinguishes it from the sibling ios_secrets_scanner, which likely overlaps heavily.

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?

Usage is implied by the pattern list — you would call this for reconnaissance of embedded URLs, keys, emails and IPs — but there is no explicit when-to-use statement, no prerequisites (e.g. whether the IPA must be decrypted), and no routing against ios_secrets_scanner.

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