droidasc-mcp

by cnlnn

Overview Schema Source Related Servers Discussions Admin

Python

Local

asc_manifest_summary

Read-only

Summarizes Android APK manifest components, filters, metadata, and static permission inheritance for triage and review.

Instructions

Read structured Manifest components, filters, metadata and permission inheritance.

Raw declarations are preserved separately. Unspecified exported defaults and resource values remain unresolved. Provider path rules and URI grants need separate review; permission inheritance is static triage, not a runtime accessibility or vulnerability test.

Input Schema

Name	Required	Description
`limit`	No	Component page size, server-capped
`offset`	No	Zero-based component offset in manifest order
`apk_path`	Yes	APK path within the configured allowed roots

Output Schema

Name	Required	Description	Default
`sdk`	No
`code`	No
`entry`	No
`items`	No
`limit`	No
`total`	No
`module`	No
`offset`	No
`status`	Yes
`backend`	No
`message`	No
`sources`	No
`apk_path`	No
`coverage`	No
`has_more`	No
`input_id`	No
`truncated`	No
`apk_sha256`	No
`session_id`	No
`application`	No
`limitations`	No
`next_offset`	No
`declarations`	No
`package_name`	No
`artifact_path`	No
`artifact_sha256`	No
`backend_version`	No
`selected_modules`	No
`application_metadata`	No
`declared_permissions`	No
`resource_values_resolved`	No
`exported_defaults_resolved`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed12 schema fields changedv0.2.5Oct 29, 2026

addedOutput schema / $defs / Entry / properties / module

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

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"
+}

Changed18 schema fields changedv0.2.4Oct 27, 2026
- removedOutput schema / $defs / Component / properties / effective_enabled / anyOf
```
Removed value: -[
-  {
-    "type": "boolean"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / $defs / Component / properties / effective_enabled / type
```
Added value: +[
+  "boolean",
+  "null"
+]
```
- removedOutput schema / $defs / Component / properties / enabled / anyOf
```
Removed value: -[
-  {
-    "type": "boolean"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / $defs / Component / properties / enabled / type
```
Added value: +[
+  "boolean",
+  "null"
+]
```
- removedOutput schema / $defs / Component / properties / exported / anyOf
```
Removed value: -[
-  {
-    "type": "boolean"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / $defs / Component / properties / exported / type
```
Added value: +[
+  "boolean",
+  "null"
+]
```
- removedOutput schema / $defs / Component / properties / name / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / $defs / Component / properties / name / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- removedOutput schema / $defs / Component / properties / target_activity / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / $defs / Component / properties / target_activity / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- removedOutput schema / $defs / Entry / properties / abi / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / $defs / Entry / properties / abi / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- removedOutput schema / $defs / Permission / properties / value / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / $defs / Permission / properties / value / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- removedOutput schema / properties / next_offset / anyOf
```
Removed value: -[
-  {
-    "type": "integer"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / next_offset / type
```
Added value: +[
+  "integer",
+  "null"
+]
```
- removedOutput schema / properties / package_name / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / package_name / type
```
Added value: +[
+  "string",
+  "null"
+]
```
Addedv0.2.3Oct 23, 2026

TDQS

A4/5.0

Behavior5/5

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

Beyond the readOnly/non-destructive annotations, it discloses real interpretive limits: exported defaults and resource values stay unresolved, and permission inheritance is 'static triage, not a runtime accessibility or vulnerability test'. That tells the agent exactly how much confidence to place in results, which no annotation conveys.

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 and each following clause carries a distinct caveat, so no sentence is filler. Phrasing is terse to the point of fragmentation, but nothing is wasted.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/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 values need not be explained; the description instead spends its budget on scope and epistemics, which is what's missing at this complexity. Combined with full parameter documentation, an agent has enough to call it and interpret results correctly.

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% and limit/offset/apk_path are each documented in the schema, including server capping and allowed roots. The description adds nothing about parameter behavior beyond the schema, so 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?

Uses a specific verb (Read) plus enumerated resources (components, filters, metadata, permission inheritance) so the agent knows the output shape. It implicitly distinguishes itself from a raw-dump sibling via 'Raw declarations are preserved separately', but never names asc_get_manifest, so the differentiation stays inferential.

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 only implied: 'Raw declarations are preserved separately' and 'need separate review' hint at when this tool stops and another begins, but no sibling is named and no explicit when-to-use condition is given. The agent must infer that asc_get_manifest covers the raw case.

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

Deploy Server