Skip to main content
Glama

Screenshot

emu_screenshot
Read-only

Capture a PNG screenshot of an Android emulator's screen, including its serial and size, for read-only inspection without acquiring a lease.

Instructions

Return a PNG screenshot of the AVD's screen (and its serial and size). Changes nothing and needs no lease; it works while another session holds the emulator, but then only look, do not act on 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_screenshot"
  }
}

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
Behavior5/5

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

Beyond readOnlyHint/destructiveHint, the description discloses concurrency behavior that annotations cannot express: it works while another session holds the emulator and requires no lease. It also adds an operational caution ("only look, do not act on it") that tells the agent how to behave in that shared state.

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?

One sentence, front-loaded with the action and return value, then the lease/concurrency constraint. Every clause carries distinct information; nothing is redundant padding.

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?

For a single-parameter read tool with no output schema, the description covers what is returned (PNG plus serial and size), the safety profile, and the concurrent-session caveat. An agent has everything needed to call it correctly 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?

There is a single optional parameter and schema coverage is 100%, with the schema documenting the default and the EMU_AVD environment variable fallback. The description adds nothing about the avd argument, which is acceptable given the schema already carries that meaning.

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 gives a specific verb and resource ("Return a PNG screenshot of the AVD's screen") and even names the return payload (serial and size). It implicitly separates itself from lease-holding siblings by noting it needs no lease, but it never names an alternative tool explicitly.

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?

It clearly states the operative context: no lease required, usable while another session holds the emulator, but in that case read-only observation only. That is strong when-to-use guidance; the only gap is that no sibling tool is named as the alternative for acting on the emulator.

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