Skip to main content
Glama
deenesjakoruzh
vs4vijay

espresso-mcp

by vs4vijay
OverviewSchemaRelated ServersScoreDiscussions
Python
Local

kill_emulator

Terminate a specific Android emulator by name to free system resources or stop unresponsive instances. This tool helps manage emulator processes in development environments.

Instructions

Kill a specific Android Emulator

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
emulator_nameYes

Implementation Reference

  • src/espresso_mcp/server.py:56-64 (handler)
    The implementation of the 'kill_emulator' tool. This handler function uses ADB to send an 'emu kill' command to the specified emulator device, terminating it. Registered via the @mcp.tool() decorator.
    @mcp.tool()
def kill_emulator(emulator_name: str) -> str:
    """Kill a specific Android Emulator"""
    result = subprocess.run(
        ["adb", "-s", emulator_name, "emu", "kill"], capture_output=True, text=True
    )
    if result.returncode != 0:
        raise RuntimeError(f"Error killing emulator '{emulator_name}': {result.stderr}")
    return f"Emulator '{emulator_name}' has been killed."

Tool Definition Quality

C2.9/5.0
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the action ('kill') but doesn't explain what 'kill' entails (e.g., forceful termination, graceful shutdown, data persistence implications), potential side effects, error conditions, or required permissions. For a destructive operation with zero annotation coverage, this is a significant gap in transparency.

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, direct sentence with zero wasted words. It front-loads the core action and resource efficiently, making it easy to parse. Every element ('Kill', 'a specific Android Emulator') earns its place by conveying essential information without redundancy.

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

Completeness2/5

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

Given the tool's complexity (a destructive operation), lack of annotations, no output schema, and low schema coverage, the description is incomplete. It doesn't cover behavioral details, error handling, or output expectations, leaving critical gaps for an AI agent to use it safely and effectively in context with sibling tools.

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?

The schema description coverage is 0%, so the description must compensate. It implies the parameter 'emulator_name' by mentioning 'a specific Android Emulator', but doesn't specify format, constraints, or how to obtain valid names (e.g., from 'list_emulators'). This adds minimal semantic value beyond the schema's title, resulting in a baseline score of 3 for partial compensation.

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 clearly states the verb ('kill') and resource ('a specific Android Emulator'), making the purpose unambiguous. It distinguishes from siblings like 'start_emulator' and 'list_emulators' by specifying termination rather than creation or listing. However, it doesn't explicitly differentiate from potential alternatives like 'stop_app' for app-level operations, keeping it at 4 rather than 5.

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?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., the emulator must be running), exclusions (e.g., not for physical devices), or comparisons to sibling tools like 'stop_app' for apps or 'list_emulators' to identify targets. This lack of contextual direction limits its utility for an AI agent.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/vs4vijay/espresso-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server