Skip to main content
Glama
Sign In
droidasc-mcp

droidasc-mcp

by cnlnn
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

asc_apk_info

Read-only

Inspect APK size, SHA-256 hash, manifest presence, and top-level DEX entries to verify package contents and support read-only Android app analysis.

Instructions

Inspect APK size, SHA-256, manifest presence, and top-level DEX entries.

Input Schema

NameRequiredDescriptionDefault
apk_pathYesAPK file path within configured allowed roots
include_sha256NoCompute a full input SHA-256 when true

Output Schema

NameRequiredDescriptionDefault
sha256No
apk_pathYes
size_bytesYes
dex_entriesYes
has_manifestYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv0.2.3
    • addedInput schema / properties / apk_path / description
      Added value: +"APK file path within configured allowed roots"
    • addedInput schema / properties / include_sha256 / description
      Added value: +"Compute a full input SHA-256 when true"
    • addedOutput schema / properties
      Added value: +{
+  "apk_path": {
+    "title": "Apk Path",
+    "type": "string"
+  },
+  "dex_entries": {
+    "items": {
+      "type": "string"
+    },
+    "title": "Dex Entries",
+    "type": "array"
+  },
+  "has_manifest": {
+    "title": "Has Manifest",
+    "type": "boolean"
+  },
+  "sha256": {
+    "title": "Sha256",
+    "type": "string"
+  },
+  "size_bytes": {
+    "title": "Size Bytes",
+    "type": "integer"
+  }
+}
    • addedOutput schema / required
      Added value: +[
+  "apk_path",
+  "size_bytes",
+  "dex_entries",
+  "has_manifest"
+]
    • changedOutput schema / title
      Previous value: -"asc_apk_infoDictOutput"New value: +"ApkInfoResult"
  2. First observedv0.1.1

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds that the tool reports size, hash, manifest presence and top-level DEX entries, but says nothing about cost, truncation of DEX listings, or behavior when the APK is malformed.

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?

One front-loaded sentence with an explicit verb and an enumerated output list; nothing redundant and nothing buried.

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?

An output schema exists and annotations cover safety, so the description does not need to explain return values. However, for a tool sitting in a dense cluster of APK/DEX inspection siblings, the absence of any routing guidance leaves the agent to guess which entry point to call.

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 description coverage is 100%, so both apk_path and include_sha256 are already documented in the schema. The description's mention of SHA-256 loosely signals that hashing is part of the output and therefore toggleable, but adds no syntax or default details beyond the schema. Baseline 3 applies.

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?

Specific verb (Inspect) plus resource (APK) and an enumerated set of outputs: size, SHA-256, manifest presence, top-level DEX entries. That is enough to know it is a lightweight overview tool, but it never distinguishes itself from siblings like asc_manifest_summary, asc_list_apk_entries, or asc_analyze_dex, which cover overlapping ground.

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?

There is no statement of when to use this versus the many overlapping siblings (asc_manifest_summary, asc_list_apk_entries, asc_analyze_dex) nor any exclusions or prerequisites. The word 'top-level' hints at a shallow scan, but the agent must infer that.

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