run-sequence-android-mcp

Overview Schema Source Related Servers Discussions Admin

Save Screenshot

android_save_screenshot

Captures a screenshot from a connected Android device or emulator and saves it as a PNG file to a specified absolute path.

Instructions

Take a screenshot and save it to a PNG file on this computer.

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": {
      "saveTo": "<saveTo>"
    },
    "name": "android_save_screenshot"
  }
}

Input Schema

Name	Required	Description	Default
`device`	No	Device id (serial or host:port). Optional -- when omitted, uses ANDROID_MCP_DEVICE env or auto-selects the connected device (physical devices preferred over emulators).
`saveTo`	Yes	Absolute path to save the screenshot to, ending with .png

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Nov 10, 2026

TDQS

B3.3/5.0

Behavior2/5

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

Annotations are empty, so the description must carry the full load of behavioral disclosure. It only states the basic action, omitting details about side effects (e.g., overwriting existing files), permission requirements, or whether the tool modifies device state. This is insufficient for a write operation.

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?

The description is a single sentence that is neither verbose nor incomplete. Every word is necessary, and it is front-loaded with the main action. Zero wasted text.

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

Completeness3/5

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

Given the tool's simplicity (1 required parameter, no output schema), the description is adequate but minimal. It does not explain the return value or what happens if the file already exists. More detail could improve completeness without redundancy.

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?

The input schema has 100% coverage and already describes both parameters adequately. The description adds no additional meaning beyond what the schema provides, so it meets the baseline but does not enhance understanding.

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's action ('Take a screenshot') and the outcome ('save it to a PNG file on this computer'). The verb 'Take' and resource 'screenshot' are specific, and the mention of saving to a file distinguishes it from the sibling tool 'android_take_screenshot', which likely captures without saving.

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 like android_take_screenshot. It does not specify prerequisites, context, or exclusion criteria, leaving the agent to infer usage from the name alone.

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