Skip to main content
Glama

list_emulators

Lists all currently running Android emulators for development and testing purposes.

Instructions

List all running Android Emulators

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler function for the 'list_emulators' tool. It runs 'adb devices' to list running Android emulators, parses the output to extract emulator IDs, and returns them as a list.
    @mcp.tool()
    def list_emulators() -> list:
        """List all running Android Emulators"""
        result = subprocess.run(["adb", "devices"], capture_output=True, text=True)
        if result.returncode != 0:
            raise RuntimeError(f"Error listing emulators: {result.stderr}")
        lines = result.stdout.splitlines()
        print("---lines", lines)
        emulators = [line.split()[0] for line in lines[1:] if "emulator" in line]
        return emulators
  • The @mcp.tool() decorator registers the list_emulators function as an MCP tool.
    @mcp.tool()
Behavior2/5

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

No annotations are provided, so the description carries full burden. It states what the tool does but lacks behavioral details such as output format (e.g., list of names, IDs, statuses), whether it includes emulator properties, error handling, or performance considerations. For a tool 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, efficient sentence with zero waste: 'List all running Android Emulators'. It is front-loaded with the core action and resource, making it immediately clear and appropriately sized for the tool's simplicity.

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 no annotations, no output schema, and a simple tool with 0 parameters, the description is minimal. It states the purpose but lacks context on what information is returned, how to interpret results, or any behavioral nuances. For even a simple tool, more completeness (e.g., output details) would help the agent use it effectively.

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 0 parameters with 100% schema description coverage, so no parameter documentation is needed. The description doesn't add param info beyond the schema, but this is acceptable given the lack of parameters. Baseline 4 is appropriate as the description doesn't need to compensate for any parameter gaps.

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 'List all running Android Emulators' clearly states the verb ('List') and resource ('running Android Emulators'), with 'all' indicating comprehensive scope. It distinguishes from siblings like 'list_avds' (which lists available virtual devices) and 'kill_emulator' (which terminates emulators), making the purpose specific and unambiguous.

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 usage when needing to see currently active emulators, but doesn't explicitly state when to use this tool versus alternatives like 'list_avds' (for available devices) or 'start_emulator' (to launch one). No guidance on prerequisites, exclusions, or comparison with siblings is provided, leaving usage context partially inferred.

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