Skip to main content
Glama

Inspect Dart Aot

inspect_dart_aot
Idempotent

Inspect a Flutter AOT snapshot inside an APK to locate its four ELF snapshot symbols, headers, hash, and string-pool package/SDK URIs for dependency mapping; choose summary or full detail.

Instructions

Inspect one ABI's Dart AOT snapshot inside an APK: the four snapshot symbols located through the ELF dynamic symbol table with their offsets, sizes, and section headers (magic, kind, length), the snapshot hash, and a bounded string-pool projection from the isolate data section (package: source URIs, dart: SDK URIs, identifier-like tokens) exposing the app's dependency structure. String-pool entries are byte-pattern observations, not deserialized cluster semantics; typed class and function recovery needs an SDK-specific parser. Omitted or complete detail returns the full observation. Select detail: "summary" for target/ABI/library identity, all snapshot headers, coverage and original lower-bound counts without string lists. The complete source stays retained; read returned strings via inspect_analysis_view with parent_evidence_id and kind dart-aot, collection package_uris/dart_uris/class_like_tokens, offset and limit. Exhausting pages does not imply complete pool coverage. No engine, no execution.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "path": "/targets/Example.apk"
    },
    "name": "inspect_dart_aot"
  }
}

Input Schema

NameRequiredDescriptionDefault
abiNoABI to inspect; defaults to arm64-v8a, x86_64, x86, armeabi-v7a, then remaining ABIs alphabetically
pathYesLocal APK file carrying a Flutter AOT payload
detailNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.6/5.0
Behavior5/5

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

Annotations only cover safety/idempotency flags, so the description carries the real burden and does: it warns that string-pool entries are byte-pattern observations rather than deserialized cluster semantics, that typed class/function recovery needs an SDK-specific parser, that paging exhaustion does not imply complete pool coverage, and that the source stays retained. 'No engine, no execution' also clarifies cost. These are meaningful caveats an agent could not infer from structured fields.

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?

Content is front-loaded: what is inspected first, then limitations, then detail modes, then the follow-up read path. Sentences are dense and semi-colon-heavy, and 'Omitted or complete detail returns the full observation' is tersely worded, but virtually nothing is filler.

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?

There is no output schema, and the description compensates by describing the return payload in concrete terms (symbols with offsets, sizes, section magic/kind/length, hash, string-pool projection) plus how to page through retained strings. For a 3-parameter read tool this is complete enough to invoke correctly.

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 coverage is 67% and the descriptions in the schema already cover path and abi defaults, so the description's main added value is explaining the semantic effect of the 'detail' enum (summary returns target/ABI/library identity, all snapshot headers, coverage and lower-bound counts without string lists). The abi default ordering is only in the schema, not the description, which is the minor gap.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The opening clause names a specific verb and resource ('Inspect one ABI's Dart AOT snapshot inside an APK') and enumerates exactly what is returned: the four snapshot symbols via the ELF dynamic symbol table, the snapshot hash, and a bounded string-pool projection. This is clearly distinguishable from siblings like inspect_binary_layout or inspect_apktool_client, and the follow-up names inspect_analysis_view as the companion reader.

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 description states the condition for using the 'summary' detail mode versus the default full observation, and explicitly routes string retrieval to inspect_analysis_view with parent_evidence_id, kind, collection, offset and limit. It stops short of saying when to choose this tool over other artifact inspectors, but the within-tool routing guidance is unusually explicit.

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