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

android-device-mcp

by prashant1507
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Execute shell command

execute_shell_command

Execute shell commands on an Android device for system management, debugging, or automation tasks.

Instructions

Execute shell command in an Android device.

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>",
      "command": "<command>"
    },
    "name": "execute_shell_command"
  }
}

Input Schema

NameRequiredDescriptionDefault
serialYes
commandYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.1/5.0
Behavior1/5

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

No annotations exist, and the description fails to disclose any behavioral traits such as potential destructive actions, need for root, output handling, or error conditions. For a shell command tool, this is a critical omission.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is overly terse (one sentence) and lacks structural elements like bullet points or context. While conciseness is valued, here it sacrifices essential information.

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

Completeness1/5

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

Given the tool's power (arbitrary shell command execution) and the absence of output schema, annotations, or parameter details, the description is severely incomplete. It does not inform the agent about return values, potential side effects, or required permissions.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 0% schema description coverage and no textual elaboration, the description adds no meaning to the two parameters (serial and command). The agent receives no hints about valid values, formats, or constraints beyond type 'string'.

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 clearly states it executes a shell command on an Android device, specifying the verb and resource. It is distinct from sibling tools which cover other ADB operations (e.g., clear logs, take screenshots). However, it could be more precise about the scope (e.g., any shell command).

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 like pulling files or installing apps. The description does not mention prerequisites, safety considerations, or context where this tool is appropriate.

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