Skip to main content
Glama

adb_mirror_stop

Stops an active scrcpy mirroring session for a specified Android device, or ends all mirroring sessions when no device is provided.

Instructions

Stop an active scrcpy mirroring session for a device.

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": "adb_mirror_stop"
  }
}

Input Schema

NameRequiredDescriptionDefault
deviceNoDevice serial (stops that device's session). Omit to stop all.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.1.6
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  2. Changed1 schema field changedv1.1.3
    • removedInput schema / additionalProperties
      Removed value: -false
  3. First observedv1.1.1

TDQS

A3.8/5.0
Behavior3/5

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

With no annotations, the description still makes the basic mutating behavior clear: an active scrcpy session is stopped for a device. It does not explain what happens when no session is active, whether the operation is idempotent, or whether any device-side state is affected.

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 single sentence is front-loaded with the action and target, with no unnecessary wording. Its brevity is appropriate for a simple lifecycle-stop tool.

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

Completeness4/5

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

Together with the fully documented optional parameter, the description provides enough information for ordinary invocation, including targeted and stop-all operation through the schema. Explicit no-session behavior and brief lifecycle guidance would make it more complete, but these are modest gaps for this simple tool.

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 device parameter already documents both the serial format and the important omit-to-stop-all behavior. The description's phrase "for a device" reinforces targeting but adds little beyond that schema.

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 uses a specific verb and resource: stopping an active scrcpy mirroring session for a device. This clearly distinguishes the tool's lifecycle role from adb_mirror_start and adb_mirror_status.

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

Usage Guidelines3/5

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

The word "active" implies that the tool is intended for an existing mirroring session. However, it gives no explicit guidance about checking adb_mirror_status first, when not to call it, or the stop-all behavior available by omitting device.

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