Skip to main content
Glama

list_avds

Retrieve all available Android Virtual Devices (AVDs) for development and testing purposes.

Instructions

List all available Android Virtual Devices (AVDs)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The main handler function for the 'list_avds' tool, decorated with @mcp.tool() for registration in FastMCP. It runs 'emulator -list-avds' via subprocess and returns the list of AVDs.
    @mcp.tool()
    def list_avds() -> list:
        """List all available Android Virtual Devices (AVDs)"""
        result = subprocess.run(["emulator", "-list-avds"], capture_output=True, text=True)
        if result.returncode != 0:
            raise RuntimeError(f"Error listing AVDs: {result.stderr}")
        return result.stdout.splitlines()
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the action but doesn't describe traits like whether it's read-only (implied by 'List'), what format the output returns (e.g., list of names or details), or any constraints (e.g., performance impact). 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 that directly states the tool's purpose without any waste. It's front-loaded with the key action and resource, making it easy to parse and understand quickly.

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?

Given the tool's low complexity (0 parameters, no output schema, no annotations), the description is minimally adequate. It states what the tool does but lacks details on output format, behavioral context, or differentiation from siblings. For a simple list tool, this is acceptable but leaves room for improvement in completeness.

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, and the input schema has 100% coverage (though empty). The description doesn't need to add parameter details, as there are none to explain. It appropriately focuses on the action without unnecessary parameter information, earning a high baseline score for this dimension.

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 ('List') and resource ('all available Android Virtual Devices (AVDs)'), making the purpose specific and understandable. However, it doesn't explicitly differentiate from sibling tools like 'list_emulators' or 'list_apps', which would require mentioning what distinguishes AVDs from emulators or apps.

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 context, prerequisites, or exclusions, such as whether it requires an emulator to be running or if it lists only local AVDs. With sibling tools like 'list_emulators' and 'list_apps', this lack of differentiation leaves usage unclear.

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