Skip to main content
Glama
Sign In
apk-preview-mcp

apk-preview-mcp

by Famel-svg
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

apk_preview_doctor

Read-only

Diagnose Android SDK, Emulator, ADB, AVDs, and connected devices to identify configuration problems. Get actionable checks for a reliable APK preview environment.

Instructions

Diagnose Android SDK, Emulator, ADB, AVDs and connected devices.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "apk_preview_doctor"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds what gets diagnosed (SDK, emulator, ADB, AVDs, connected devices) but does not disclose output formatting or other behavioral details, though the output schema covers return structure.

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 a single sentence with no filler, and the primary purpose is stated upfront. Every word contributes to meaning.

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?

For a read-only diagnostic tool with no parameters and an output schema, the description is fully sufficient. It identifies the tool's scope and, combined with annotations and output schema, gives an agent what it needs to use the tool 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?

The tool has zero parameters, so there is no parameter semantics to document; the baseline for 0 params is 4. The description correctly omits parameter information that would be irrelevant.

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 uses a specific verb, 'Diagnose', and names a clear resource set: Android SDK, Emulator, ADB, AVDs, and connected devices. This distinguishes it from sibling tools that install APKs, launch apps, or manage sessions.

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?

The description implies a health-check or troubleshooting purpose, which makes it reasonable to run when diagnosing environment issues. However, it does not explicitly state when to use this tool versus the specific sibling operations, nor when not to use it.

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