droidasc-mcp

Overview Schema Source Related Servers Discussions Admin

asc_signing_inventory

Read-only

Inventory Android APK signing containers (v1/v2/v3) and certificate fingerprints, and detect v3.1 block presence to support signing structure checks.

Instructions

Inventory v1/v2/v3 containers and certificate fingerprints; detect v3.1 block presence.

Container presence is independent of cryptographic validity. APK digests, signatures, trust, rotation lineage and v4 sidecars remain unverified. Malformed containers produce explicit diagnostics. v1 certificates are a PKCS7 bag, not resolved signer identities.

Input Schema

Name	Required	Description	Default
`apk_path`	Yes	APK path within configured allowed roots

Output Schema

Name	Required	Description	Default
`code`	No
`limit`	No
`total`	No
`module`	No
`offset`	No
`status`	Yes
`backend`	No
`message`	No
`schemes`	No
`sources`	No
`apk_path`	No
`coverage`	No
`has_more`	No
`input_id`	No
`truncated`	No
`apk_sha256`	No
`session_id`	No
`v4_sidecar`	No
`diagnostics`	No
`limitations`	No
`next_offset`	No
`artifact_path`	No
`artifact_sha256`	No
`backend_version`	No
`selected_modules`	No
`certificate_trust`	No
`apk_content_integrity`	No
`unknown_signing_block_ids`	No
`cryptographic_verification`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed11 schema fields changedv0.2.5Oct 29, 2026

addedOutput schema / $defs / Source / properties / container_sha256

Added value: +{
+  "title": "Container Sha256",
+  "type": "string"
+}

addedOutput schema / $defs / Source / properties / container_size_bytes

Added value: +{
+  "title": "Container Size Bytes",
+  "type": "integer"
+}

addedOutput schema / $defs / Source / properties / logical_header_offset

Added value: +{
+  "title": "Logical Header Offset",
+  "type": "integer"
+}

addedOutput schema / $defs / Source / properties / logical_size_bytes

Added value: +{
+  "title": "Logical Size Bytes",
+  "type": "integer"
+}

addedOutput schema / $defs / Source / properties / module

Added value: +{
+  "title": "Module",
+  "type": "string"
+}

addedOutput schema / $defs / Source / properties / normalization

Added value: +{
+  "title": "Normalization",
+  "type": "string"
+}

addedOutput schema / $defs / Source / properties / original_dex_version

Added value: +{
+  "title": "Original Dex Version",
+  "type": "string"
+}

addedOutput schema / $defs / Source / properties / snapshot_entry

Added value: +{
+  "title": "Snapshot Entry",
+  "type": "string"
+}

addedOutput schema / $defs / Source / properties / stored_size_bytes

Added value: +{
+  "title": "Stored Size Bytes",
+  "type": "integer"
+}

addedOutput schema / properties / module

Added value: +{
+  "title": "Module",
+  "type": "string"
+}

addedOutput schema / properties / selected_modules

Added value: +{
+  "items": {
+    "type": "string"
+  },
+  "title": "Selected Modules",
+  "type": "array"
+}

Changed6 schema fields changedv0.2.4Oct 27, 2026
- removedOutput schema / $defs / Certificate / properties / public_key_bits / anyOf
```
Removed value: -[
-  {
-    "type": "integer"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / $defs / Certificate / properties / public_key_bits / type
```
Added value: +[
+  "integer",
+  "null"
+]
```
- removedOutput schema / $defs / SigningScheme / properties / container_present / anyOf
```
Removed value: -[
-  {
-    "type": "boolean"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / $defs / SigningScheme / properties / container_present / type
```
Added value: +[
+  "boolean",
+  "null"
+]
```
- removedOutput schema / properties / next_offset / anyOf
```
Removed value: -[
-  {
-    "type": "integer"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / next_offset / type
```
Added value: +[
+  "integer",
+  "null"
+]
```
Addedv0.2.3Oct 23, 2026

TDQS

A4.1/5.0

Behavior5/5

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

Beyond the readOnly/destructive annotations, the description discloses substantive behavioral traits: presence is independent of cryptographic validity, digests and v4 sidecars stay unverified, malformed containers yield explicit diagnostics, and v1 certificates are a raw PKCS7 bag rather than resolved signer identities. These caveats directly shape how an agent should interpret results and are not derivable from the annotations or schema.

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?

The capability statement is front-loaded in the first sentence, followed by a compact list of limitations, with no filler. The caveat block is dense and slightly fragmented across line breaks, but every clause carries distinct informational value.

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?

An output schema exists, so return-value details are not required, and the description covers scope, limitations, and malformed-input behavior. It could go slightly further on error conditions for unreadable paths, but for a one-parameter read-only inventory tool it is essentially complete.

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?

The single apk_path parameter is fully documented in the schema (100% coverage, including the allowed-roots constraint). The description adds no additional semantics about the path argument, so the schema does the work and the baseline of 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?

The first sentence names a specific verb and resource: inventory v1/v2/v3 containers, certificate fingerprints, and v3.1 block presence. That is clearly distinguishable from siblings like asc_apk_info and asc_inspect_artifact, which cover broader artifact metadata, even though no sibling is named explicitly.

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

Usage Guidelines4/5

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

The second paragraph effectively scopes the tool by stating what it does NOT do — no digest, signature, trust, or rotation-lineage verification — which implicitly routes verification work elsewhere. It stops short of naming an alternative tool or an explicit 'use this when' condition, so it is clear context rather than full routing guidance.

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

Deploy Server