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

apk-preview-mcp

by Famel-svg
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

apk_preview_stop_session

Stop an active Android emulator session, keeping the AVD and artifacts intact for future use.

Instructions

Stop active emulator without deleting AVD or artifacts.

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_stop_session"
  }
}

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.5/5.0
Behavior4/5

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

The description adds valuable behavioral context by clarifying that stopping the emulator does not delete the AVD or artifacts, which complements the annotations. It does not disclose what happens if no active emulator exists or whether state is saved, but the annotations already signal this is not a destructive operation.

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 entire description is a single, front-loaded sentence with no wasted words. It states the action, the target, and the important non-destructive guarantee in concise form.

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 simple zero-parameter stop operation with an output schema and annotations present, the description is complete. It gives the agent the essential purpose and the key safety property, and nothing critical is missing for correct tool selection.

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, and the input schema covers everything. The description therefore does not need to explain parameter semantics, and the 0-parameter baseline of 4 is appropriate.

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 ('Stop') with a clear resource ('active emulator') and explicitly states the non-destructive scope ('without deleting AVD or artifacts'). This clearly distinguishes the tool from its siblings such as apk_preview_start_session and apk_preview_doctor.

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 phrase 'Stop active emulator' clearly indicates when to use the tool, and 'without deleting AVD or artifacts' provides an explicit exclusion that helps an agent understand this is not a teardown/delete operation. It does not explicitly name alternatives, but the sibling list and the action itself make the usage context unambiguous.

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