Skip to main content
Glama

android_native_libraries

Enumerate every ELF .so in an APK by ABI, identify known packer/RASP/framework/SDK libraries by name, and inspect ELF headers to detect stripped or packed section tables.

Instructions

Enumerates every ELF .so shipped in an APK (per ABI), identifies known packer/RASP/framework/SDK libraries by name, and inspects ELF headers for stripped-or-packed section tables.

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": {
      "apk_path": "<apk_path>"
    },
    "name": "android_native_libraries"
  }
}

Input Schema

NameRequiredDescriptionDefault
apk_pathYesAbsolute path to the APK file to inspect

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.3.0

TDQS

B3.4/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full behavioral burden. It implies a passive read-only inspection and discloses the three analytical passes performed, which is meaningful context. However, it does not explicitly confirm read-only behavior, say what happens with non-ELF or non-APK input, or describe the shape of the result beyond 'enumerates/identifies'.

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?

One dense sentence with three parallel clauses, each carrying distinct information and no filler. The core enumeration behavior is front-loaded before the detection and header-inspection details. It is slightly packed but nothing is redundant.

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 single-parameter analysis tool with no output schema and no annotations, the description covers what is inspected but not what is returned or how results are organized (per-ABI grouping, library classification labels). An agent knows what the tool examines but not what it will receive back.

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?

There is a single parameter with 100% schema description coverage, so the schema already defines apk_path as an absolute path to the APK. The description adds no additional semantics for that parameter (e.g., handling of split APKs, relative paths, or missing files). Baseline 3 applies when the schema does the heavy lifting.

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?

The description uses a specific verb and resource — 'Enumerates every ELF .so shipped in an APK (per ABI)' — plus two additional capabilities (known-library identification, ELF header inspection for stripped/packed section tables). That is far more specific than a name restatement and clearly separates it from manifest/permissions/secrets siblings. It stops short of naming a sibling it is not, which keeps it at 4 rather than 5.

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 rather than stated: the mention of packer/RASP detection and stripped section tables signals the investigative scenarios this tool serves. There is no explicit when-to-use instruction, no prerequisites (e.g., requires a valid APK path), and no exclusions pointing to alternative APK tools.

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