Skip to main content
Glama
Sign In
android-device-mcp

android-device-mcp

by prashant1507
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Take Screenshot

take_screenshot

Capture a screenshot from an Android device by specifying its serial number and optional local file path.

Instructions

Capture a screenshot from an Android device using its serial number.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "serial": "<serial>"
    },
    "name": "take_screenshot"
  }
}

Input Schema

NameRequiredDescriptionDefault
serialYes
local_file_pathNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations, the description carries full burden. It fails to disclose key behaviors such as where the screenshot is saved (locally via local_file_path vs. returned as output), file format, permissions required, or whether it is destructive.

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 a single, concise sentence with no fluff. It is appropriately front-loaded but slightly under-specified.

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 no output schema, no annotations, and two parameters (one optional), the description is incomplete. It lacks essential context about return values, file handling, and operational constraints.

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 coverage is 0%, so the description should compensate. However, it only mentions the serial parameter by name ('serial number') and gives no explanation of local_file_path, its default behavior, or how the output is handled.

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?

The description clearly states the tool captures a screenshot from an Android device using serial number. This is a specific verb and resource, and it effectively distinguishes from siblings like 'screen_recording' (video) and 'dump_screen' (UI dump).

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?

No guidance is provided on when to use this tool versus alternatives (e.g., screen_recording, dump_screen). There are no prerequisites, conditions, or exclusions mentioned.

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

Deploy Server

Other Tools