droidasc-mcp

Overview Schema Source Related Servers Discussions Admin

asc_open_artifact_session

Creates an immutable, reusable DEX session from APK, JAR, AAR, AAB, APKS, XAPK, or ZIP inputs using container hashes, so you can safely query selected classes.

Instructions

Snapshot selected direct DEX into an immutable reusable session with container hashes.

Direct DEX at arbitrary archive paths, AAR classes.jar DEX and selected AAB modules are supported. Pure JVM classes and nested split APKs stay inventory-only. Duplicate classes are rejected. Query and close the resulting ID with the existing DEX session tools.

Input Schema

Name	Required	Description
`module`	No	AAB exact module, 1-100 distinct names, or * for all; omitted selects base
`artifact_path`	Yes	APK/JAR/AAR/AAB/APKS/XAPK/ZIP input within allowed roots
`max_uncompressed_bytes`	No	Expanded JAR/DEX bytes; disk reservation scales with this budget

Output Schema

Name	Required	Description	Default
`code`	No
`depth`	No
`edges`	No
`index`	No
`items`	No
`limit`	No
`nodes`	No
`total`	No
`format`	No
`groups`	No
`module`	No
`offset`	No
`source`	No
`status`	Yes
`backend`	No
`message`	No
`sources`	No
`apk_path`	No
`coverage`	No
`has_more`	No
`input_id`	No
`dex_entry`	No
`direction`	No
`max_edges`	No
`max_nodes`	No
`span_unit`	No
`truncated`	No
`apk_sha256`	No
`class_name`	No
`edge_count`	No
`input_kind`	No
`limit_unit`	No
`node_count`	No
`session_id`	No
`source_end`	No
`superclass`	No
`total_unit`	No
`type_match`	No
`edge_counts`	No
`field_count`	No
`limitations`	No
`method_name`	No
`next_cursor`	No
`next_offset`	No
`query_cache`	No
`scan_errors`	No
`access_flags`	No
`has_manifest`	No
`method_count`	No
`source_start`	No
`stored_bytes`	No
`artifact_path`	No
`dynamic_sites`	No
`source_sha256`	No
`type_relation`	No
`engine_version`	No
`returned_sites`	No
`artifact_sha256`	No
`backend_version`	No
`candidate_count`	No
`cleanup_pending`	No
`page_limited_by`	No
`scanned_methods`	No
`type_descriptor`	No
`definition_count`	No
`field_descriptor`	No
`idle_ttl_seconds`	No
`reference_format`	No
`selected_modules`	No
`unresolved_sites`	No
`member_references`	No
`method_descriptor`	No
`truncation_reasons`	No
`unresolved_matches`	No
`reference_semantics`	No
`response_byte_limit`	No
`methods_without_code`	No
`reserved_index_bytes`	No
`runtime_completeness`	No
`scanned_instructions`	No
`hierarchy_cycle_detected`	No
`instruction_scan_complete`	No
`runtime_target_resolution`	No
`unresolved_sites_truncated`	No
`traversal_complete_within_depth`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed25 schema fields changedv0.2.5Oct 29, 2026

changedInput schema / properties / module / anyOf

Previous value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "type": "string"
+  },
+  {
+    "items": {
+      "type": "string"
+    },
+    "type": "array"
+  },
+  {
+    "type": "null"
+  }
+]

changedInput schema / properties / module / description

Previous value: -"Exact AAB module; omitted selects base"New value: +"AAB exact module, 1-100 distinct names, or * for all; omitted selects base"

addedOutput schema / $defs / DexRow / properties / target_index

Added value: +{
+  "title": "Target Index",
+  "type": "integer"
+}

addedOutput schema / $defs / ReferenceGroup

Added value: +{
+  "additionalProperties": true,
+  "properties": {
+    "caller": {
+      "title": "Caller",
+      "type": "string"
+    },
+    "dex_entry": {
+      "title": "Dex Entry",
+      "type": "string"
+    },
+    "evidence": {
+      "items": {
+        "$ref": "#/$defs/DexRow"
+      },
+      "title": "Evidence",
+      "type": "array"
+    },
+    "matches": {
+      "items": {
+        "type": "string"
+      },
+      "title": "Matches",
+      "type": "array"
+    },
+    "offset_unit": {
+      "title": "Offset Unit",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "target_field": {
+      "enum": [
+        "callee",
+        "field_descriptor",
+        "value",
+        "type_descriptor"
+      ],
+      "title": "Target Field",
+      "type": "string"
+    }
+  },
+  "required": [
+    "dex_entry",
+    "caller",
+    "target_field",
+    "matches",
+    "evidence"
+  ],
+  "title": "ReferenceGroup",
+  "type": "object"
+}

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 / groups

Added value: +{
+  "items": {
+    "$ref": "#/$defs/ReferenceGroup"
+  },
+  "title": "Groups",
+  "type": "array"
+}

addedOutput schema / properties / limit_unit

Added value: +{
+  "const": "caller_groups",
+  "title": "Limit Unit",
+  "type": "string"
+}

addedOutput schema / properties / module

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

addedOutput schema / properties / next_cursor

Added value: +{
+  "title": "Next Cursor",
+  "type": [
+    "string",
+    "null"
+  ]
+}

removedOutput schema / properties / page_limited_by / const
```
Removed value: -"response_bytes"
```

addedOutput schema / properties / page_limited_by / enum

Added value: +[
+  "response_bytes",
+  "caller_groups"
+]

addedOutput schema / properties / reference_format

Added value: +{
+  "const": "grouped",
+  "title": "Reference Format",
+  "type": "string"
+}

addedOutput schema / properties / returned_sites

Added value: +{
+  "title": "Returned Sites",
+  "type": "integer"
+}

addedOutput schema / properties / selected_modules

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

addedOutput schema / properties / total_unit

Added value: +{
+  "const": "reference_sites",
+  "title": "Total Unit",
+  "type": "string"
+}

addedOutput schema / properties / type_match

Added value: +{
+  "enum": [
+    "exact",
+    "substring"
+  ],
+  "title": "Type Match",
+  "type": "string"
+}

addedOutput schema / properties / type_relation

Added value: +{
+  "title": "Type Relation",
+  "type": "string"
+}

Changed18 schema fields changedv0.2.4Oct 27, 2026

removedOutput schema / $defs / DexRow / properties / instruction_offset / anyOf

Removed value: -[
-  {
-    "type": "integer"
-  },
-  {
-    "type": "null"
-  }
-]

addedOutput schema / $defs / DexRow / properties / instruction_offset / type
```
Added value: +[
+  "integer",
+  "null"
+]
```

removedOutput schema / $defs / DexRow / properties / offset_unit / anyOf

Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]

addedOutput schema / $defs / DexRow / properties / offset_unit / type
```
Added value: +[
+  "string",
+  "null"
+]
```

removedOutput schema / $defs / DexRow / properties / target_dex_entry / anyOf

Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]

addedOutput schema / $defs / DexRow / properties / target_dex_entry / type
```
Added value: +[
+  "string",
+  "null"
+]
```

removedOutput schema / $defs / GraphNode / properties / dex_entry / anyOf

Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]

addedOutput schema / $defs / GraphNode / properties / dex_entry / type
```
Added value: +[
+  "string",
+  "null"
+]
```

removedOutput schema / $defs / GraphNode / properties / without_code / anyOf

Removed value: -[
-  {
-    "type": "boolean"
-  },
-  {
-    "type": "null"
-  }
-]

addedOutput schema / $defs / GraphNode / properties / without_code / type
```
Added value: +[
+  "boolean",
+  "null"
+]
```

addedOutput schema / $defs / QueryCache / properties / budget_bytes

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

addedOutput schema / $defs / QueryCache / properties / stored_bytes

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

removedOutput schema / properties / next_offset / anyOf

Removed value: -[
-  {
-    "type": "integer"
-  },
-  {
-    "type": "null"
-  }
-]

addedOutput schema / properties / next_offset / type
```
Added value: +[
+  "integer",
+  "null"
+]
```

addedOutput schema / properties / page_limited_by

Added value: +{
+  "const": "response_bytes",
+  "title": "Page Limited By",
+  "type": "string"
+}

addedOutput schema / properties / response_byte_limit

Added value: +{
+  "title": "Response Byte Limit",
+  "type": "integer"
+}

removedOutput schema / properties / superclass / anyOf

Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]

addedOutput schema / properties / superclass / type
```
Added value: +[
+  "string",
+  "null"
+]
```

Addedv0.2.3Oct 23, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already disclose that this is not read-only, not destructive, and closed-world; the description adds useful context that it creates an immutable reusable session with hashes. It also discloses that duplicate classes are rejected and that some inputs stay inventory-only. It does not mention permission requirements or other operational constraints beyond the schema's byte budget.

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?

The description is short, front-loaded with the core action, and each additional sentence adds useful scope or follow-up information. There is no redundant restatement of the tool name or schema fields.

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?

Given the annotations, 100% schema coverage, and an output schema, the description provides enough context to invoke the tool correctly. It covers supported inputs, limitations, duplicate handling, and how to use the resulting session ID.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the baseline is 3. The description adds meaningful context for artifact_path and module by explaining supported artifact forms, selected AAB modules, and inventory-only cases. It does not add much beyond the schema for max_uncompressed_bytes, but the schema already documents that parameter.

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 states a specific verb and resource: it snapshots selected direct DEX into an immutable reusable session with container hashes. It also scopes supported artifact types and limitations. It does not explicitly distinguish this from the sibling asc_open_dex_session, so it falls short of full sibling differentiation.

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?

It clearly indicates supported contexts: direct DEX at archive paths, AAR classes.jar DEX, and selected AAB modules, while noting that pure JVM classes and nested split APKs remain inventory-only. It also says to query and close the resulting ID with existing DEX session tools. It does not explicitly name when to prefer asc_open_dex_session instead.

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

Deploy Server