Skip to main content
Glama

Identify Flutter Build

identify_flutter_build
Idempotent

Parses a local APK to extract Flutter build facts such as Dart VM snapshot hashes, per-ABI library digests, engine build IDs, and version strings without executing code.

Instructions

Identify a Flutter app's build facts by pure parsing: the Dart VM snapshot hash from every lib//libapp.so AOT section (vm and isolate, cross-checked), per-ABI library digests, the engine library's GNU build-id, and any labeled Dart version or toolchain strings libflutter.so carries. The snapshot hash is the artifact that maps to a Dart SDK release through an external dataset; REA performs no lookup. No engine, no execution, no external tools.

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": "identify_flutter_build"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYesLocal APK file to inspect

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior4/5

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

The description goes well beyond the annotations by disclosing the analysis technique (static parsing of libapp.so AOT sections and libflutter.so strings), the cross-check between vm and isolate hashes, and the key limitation that no SDK lookup is performed. The 'no engine, no execution, no external tools' guarantee is exactly the kind of behavioral context an agent needs. It does not explain why readOnlyHint is false, but nothing in the text contradicts that annotation.

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?

Front-loaded with the action and the extracted artifacts, followed by the crucial caveat about the external dataset and the no-execution guarantee. The density is justified by the tool's complexity, though the single long second sentence packed with artifact names could be broken up for faster scanning.

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?

With no output schema, the description correctly compensates by enumerating the returned facts (snapshot hash, digests, build-id, version strings), so an agent knows what to expect. It stops short of describing result structure or failure behavior for non-Flutter or malformed APKs, which is the remaining gap.

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?

Only one parameter (path, a local APK) and schema description coverage is 100%, so the schema already carries the parameter's meaning. The description adds no further detail about the input file—whether it must be a local path, what happens on non-Flutter APKs, or size/format constraints—so baseline 3 applies.

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?

States a specific verb and resource ('Identify a Flutter app's build facts') and then enumerates exactly what is extracted: VM snapshot hash per ABI, per-ABI library digests, GNU build-id, and Dart/toolchain strings. The 'pure parsing' framing plus the explicit 'no engine, no execution, no external tools' scope distinguishes it from binary-execution or session-based siblings.

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 implied rather than stated: the 'pure parsing / no execution' framing tells an agent this is the static route, and the note that snapshot-hash-to-SDK mapping is done elsewhere signals a follow-up step. However, it never says when to prefer this tool over alternatives, nor does it name any sibling or prerequisite condition (e.g. requires an already-unpacked APK).

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