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

apk-preview-mcp

by Famel-svg
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

apk_preview_interact

Simulate taps at specified coordinates or press Android navigation keys (back, home, recents) to interact with an app preview on the emulator.

Instructions

Tap coordinates or press an allowed Android navigation key.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "action": "<action>"
    },
    "name": "apk_preview_interact"
  }
}

Input Schema

NameRequiredDescriptionDefault
xNo
yNo
actionYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

The description states the operation (send tap or navigation key events) but does not disclose side effects, coordinate-system assumptions, or that navigation actions may leave the app context. Annotations are present and not contradicted, so the lowered bar is met but not exceeded.

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?

The description is one short sentence with no filler, and the main verb is front-loaded. It is appropriately concise for a simple tool, though it spends no words on usage context.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With an output schema available and a simple action enum, this is minimally adequate. Missing context includes prerequisites (active session) and the relationship between action values and x/y requirements, but the core invocation is understandable from the description plus schema.

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?

Schema description coverage is 0%, so the description must compensate. It adds useful grouping: x/y are 'coordinates' for tapping, and action corresponds to a navigation key. However, it does not clarify that x/y are only needed for tap, that x/y are nullable, or that action is required.

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 uses specific verbs ('tap', 'press') and identifies the input resource: screen coordinates and Android navigation keys. It is clearly the interaction tool among the apk_preview_* siblings, though it does not explicitly name the running preview session as the target.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no guidance on when to choose this tool over siblings or what state is required (e.g., an active preview session). The context is only implied by the verb 'tap'/'press'; no exclusions or alternatives are mentioned.

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