Skip to main content
Glama
jramalho

AVD MCP Server

by jramalho
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Local

Server Quality Checklist

58%
Profile completionA complete profile improves this server's visibility in search results.

  • Latest release: v0.1.0

  • Disambiguation5/5

    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.

    Naming Consistency5/5

    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.

    Tool Count2/5

    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.

    Completeness1/5

    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.

  • Average 2.7/5 across 1 of 1 tools scored.

    See the Tool Scores section below for per-tool breakdowns.

    • No community issues in the last 6 months
    • 0 commits in the last 12 weeks
    • No stable releases found
    • No critical vulnerability alerts
    • No high-severity vulnerability alerts
    • No code scanning findings
    • CI status not available

  • This repository is licensed under MIT License.

  • This repository includes a README.md file.

  • No tool usage detected in the last 30 days. Usage tracking helps demonstrate server value.

    Tip: use the "Try in Browser" feature on the server page to seed initial usage.

  • Add a glama.json file to provide metadata about your server.

  • If you are the author, simply .

    If the server belongs to an organization, first add glama.json to the root of your repository:

    {
  "$schema": "https://glama.ai/mcp/schemas/server.json",
  "maintainers": [
    "your-github-username"
  ]
}

    Then . Browse examples.

  • Add related servers to improve discoverability.

How to sync the server with GitHub?

Servers are automatically synced at least once per day, but you can also sync manually at any time to instantly update the server profile.

To manually sync the server, click the "Sync Server" button in the MCP server admin interface.

How is the quality score calculated?

The overall quality score combines two components: Tool Definition Quality (70%) and Server Coherence (30%).

Tool Definition Quality measures how well each tool describes itself to AI agents. Every tool is scored 1–5 across six dimensions: Purpose Clarity (25%), Usage Guidelines (20%), Behavioral Transparency (20%), Parameter Semantics (15%), Conciseness & Structure (10%), and Contextual Completeness (10%). The server-level definition quality score is calculated as 60% mean TDQS + 40% minimum TDQS, so a single poorly described tool pulls the score down.

Server Coherence evaluates how well the tools work together as a set, scoring four dimensions equally: Disambiguation (can agents tell tools apart?), Naming Consistency, Tool Count Appropriateness, and Completeness (are there gaps in the tool surface?).

Tiers are derived from the overall score: A (≥3.5), B (≥3.0), C (≥2.0), D (≥1.0), F (<1.0). B and above is considered passing.

Tool Scores

  • 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 mentions starting an AVD, running a command, and taking a screenshot, but lacks details on permissions required, whether the AVD persists after execution, error handling, or what the screenshot output entails (e.g., format, storage location). For a tool with multiple actions and no 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.

    Conciseness4/5

    Is the description appropriately sized, front-loaded, and free of redundancy?

    The description is concise and front-loaded in a single sentence: 'Sobe AVD se necessário, roda comando (pnpm/gradle/etc) e tira screenshot.' It efficiently outlines the main actions without unnecessary words, though it could be slightly more structured by separating the steps for clarity.

    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 complexity (multiple actions: start AVD, run command, take screenshot), no annotations, no output schema, and 0% schema description coverage, the description is incomplete. It doesn't address key aspects like what happens if the AVD fails to start, how commands are executed, or what the tool returns (e.g., screenshot data or success status), leaving the agent with insufficient information for reliable use.

    Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

    Parameters2/5

    Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

    Schema description coverage is 0%, meaning parameters are undocumented in the schema. The description doesn't add any meaning beyond the parameter names: it doesn't explain what 'avdName' refers to, what types of 'command' are valid, or the purpose of 'waitMsAfterRun'. With three parameters and no schema descriptions, the description fails to compensate for this lack of coverage.

    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 tool's purpose: 'Sobe AVD se necessário, roda comando (pnpm/gradle/etc) e tira screenshot.' This translates to 'Starts AVD if necessary, runs a command (pnpm/gradle/etc) and takes a screenshot.' It specifies the verb (start, run, take screenshot) and resource (AVD, command execution). However, since there are no sibling tools, it doesn't need to differentiate from alternatives, so it doesn't achieve the highest score of 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, scenarios where it's appropriate, or any exclusions. The phrase 'se necessário' (if necessary) implies some conditional usage but doesn't specify what makes it necessary, leaving the agent with minimal context for decision-making.

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

GitHub Badge

Glama performs regular codebase and documentation scans to:

  • Confirm that the MCP server is working as expected.
  • Confirm that there are no obvious security issues.
  • Evaluate tool definition quality.

Our badge communicates server capabilities, safety, and installation instructions.

Card Badge

avd-mcp MCP server

Copy to your README.md:

Score Badge

avd-mcp MCP server

Copy to your README.md:

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/jramalho/avd-mcp'

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