Skip to main content
Glama

apk_inspect

Fingerprints APK/AAR files across Flutter, React Native, Hermes, Unity IL2CPP, Kotlin, and native libraries, and can harvest URLs and API routes from DEX files.

Instructions

Fingerprint an APK/AAR (Flutter, React Native, Hermes, Unity IL2CPP, Kotlin, native libs) and optionally harvest URLs / API routes from its DEX files.

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": {
      "path": "<path>"
    },
    "name": "apk_inspect"
  }
}

Input Schema

NameRequiredDescriptionDefault
modeNotriage
pathYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full burden. "Inspect/fingerprint" implies read-only analysis, but it says nothing about side effects, file-size or time limits, whether it unpacks archives on disk, or what the results contain; the framework list adds scope but not behavioral disclosure.

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?

A single front-loaded sentence with no filler; the parenthetical framework list is dense but earns its place by helping an agent recognize supported targets. It could be split to surface the mode distinction earlier.

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?

For a two-parameter analysis tool with no annotations and no output schema, the definition covers the what but not the result: it never indicates what a fingerprint contains (frameworks detected, signatures, hashes) or how URL/route results are returned, leaving the agent to guess at output shape.

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 0%, so the description must compensate. "Optionally harvest URLs / API routes from DEX files" effectively explains the mode=apis branch versus the default triage fingerprinting, which is real added meaning, but the path parameter's semantics (file vs. directory, absolute/relative, AAR vs. APK handling) remain unstated.

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 specific verb ("Fingerprint") and resource (APK/AAR) plus the frameworks it can recognize, and the optional URL/API-route harvesting from DEX files. It is distinguishable from generic binary siblings like triage_binary or extract_strings, though it never names an overlapping alternative explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The word "optionally" hints that URL harvesting is a secondary behavior, but there is no guidance on when to pick this tool over extract_strings, imports_exports, or triage_binary, and no mention of prerequisites such as an unpacked APK vs. a raw archive.

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