Skip to main content
Glama

Inspect Apktool Client

inspect_apktool_client
Idempotent

Resolve and report the selected Apktool launcher's command, selection source, and version so you can verify configuration before decoding; it performs no decoding.

Instructions

Inspect the caller-selected apktool launcher: resolved command, selection source, and version. Decodes nothing. REA never installs Apktool or Java; select a launcher with REA_APKTOOL_COMMAND (absolute) or apktool on PATH.

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": {},
    "name": "inspect_apktool_client"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior3/5

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

Annotations already declare openWorldHint=true, idempotentHint=true, and destructiveHint=false. The description usefully adds that REA never installs Apktool or Java and that no decoding occurs, but it does not explain why readOnlyHint is false or whether version lookup executes the launcher.

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 front-loaded and compact: purpose and returned values come first, followed by non-actions and selection configuration. Every sentence contributes useful information without repetition.

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?

For a zero-parameter, no-output-schema inspection tool, it sufficiently explains what is inspected, what is returned, and how the launcher is selected. The main remaining gap is the unexplained readOnlyHint=false and whether version inspection invokes the launcher.

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?

There are zero parameters, so the empty schema provides no parameter semantics to compensate for. The description adds useful selection context by naming REA_APKTOOL_COMMAND and PATH, which helps the agent understand how the launcher is chosen.

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 description states a specific verb and resource: inspect the caller-selected apktool launcher. It names exactly what is returned (resolved command, selection source, version) and explicitly says it decodes nothing, which distinguishes it from decoding tools.

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 gives clear context that this is for checking the selected Apktool launcher and not for decoding, and explains how a launcher is selected via REA_APKTOOL_COMMAND or PATH. It does not explicitly compare against sibling inspect tools or state when not to use this tool.

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