Skip to main content
Glama

Emulator status

emu_status
Read-onlyIdempotent

Show the current lease owner and validity, running emulators, AVD serial and boot state, adb version, and resolved SDK/adb/lab paths without changing anything or needing a lease.

Instructions

Show the lease of the AVD (owner, until, valid, mine), the running emulators, the AVD's serial and boot state, the adb version and the resolved paths (SDK root, AVD home, adb, lab home). Changes nothing and needs no lease. If the lease belongs to another owner and is valid, the emulator is BUSY: wait or ask the person, do not use it.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "emu_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
avdNoAVD name (default "unity-test", or the EMU_AVD environment variable of the server).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), but the description adds genuinely new behavior: no lease is required to call it, and the BUSY/ownership condition governs downstream actions. That ownership-conflict guidance is the kind of operational nuance annotations cannot express.

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?

A single dense paragraph that front-loads the returned information, then the no-side-effects/no-lease guarantee, then the BUSY warning. Every clause carries information and nothing is repeated from the schema or annotations.

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

Completeness5/5

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

There is no output schema, so the description takes on the job of describing return contents and does so field-by-field, including diagnostics like adb version and resolved paths. Combined with the lease-conflict rule, an agent has everything needed to call it and interpret the result.

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?

Schema description coverage is 100% and the single optional 'avd' parameter already documents its default and the EMU_AVD environment fallback. The description never mentions the parameter, so it adds no meaning beyond the schema; baseline 3 applies.

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?

States a specific verb (Show) and enumerates exactly what is reported: lease fields (owner, until, valid, mine), running emulators, serial and boot state, adb version, and resolved paths. This is clearly a status/inspection tool and is distinguishable at a glance from mutating siblings such as emu_start, emu_release, or emu_renew.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives explicit context ('Changes nothing and needs no lease') and a concrete when-not-to-proceed rule: if the lease is valid and owned by someone else, the emulator is BUSY and the agent should wait or ask the person rather than use it. It stops short of naming a specific sibling to call instead, so it is clear context rather than a full routing rule.

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