AVD MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| avd_run_and_screenshotC | Sobe AVD se necessário, roda comando (pnpm/gradle/etc) e tira screenshot. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 1 tool
With only one tool, there is no possibility of ambiguity or overlap between tools. The tool's purpose is clearly defined as running commands and taking screenshots in an AVD environment.
Since there is only one tool, naming consistency is inherently perfect. The tool name 'avd_run_and_screenshot' follows a clear verb-based pattern, though with a single tool, consistency across a set cannot be assessed.
One tool is too few for a server named 'AVD MCP Server', which suggests a broader scope related to Android Virtual Device operations. A single tool covering both command execution and screenshot capture feels thin and incomplete for the domain.
The tool surface is severely incomplete for an AVD-focused server. There are obvious gaps such as creating/starting/stopping AVDs, managing device states, installing apps, or performing other common AVD operations, leaving agents unable to handle typical workflows.