Skip to main content
Glama
Sign In
android-mcp

android-mcp

by ibrahimali111
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

android_shell

Run ADB shell commands directly on an Android device to inspect settings, manage apps, or automate tasks without opening a terminal.

Instructions

Execute an ADB shell command directly on the 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": {
      "command": "<command>"
    },
    "name": "android_shell"
  }
}

Input Schema

NameRequiredDescriptionDefault
commandYesShell command to run

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?

No annotations are provided, so the description carries the full burden. It does not disclose whether the command runs as a specific user, sandboxing, timeout, output capture, error handling, or whether it is destructive — all critical for an arbitrary shell executor.

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?

Single, front-loaded, zero-waste sentence.

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?

For an arbitrary shell execution tool with no annotations and no output schema, the description omits essential behavioral context (result format, limits, permissions, risk profile) an agent needs to invoke it safely.

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 coverage is 100% with a single documented 'command' parameter. The description adds no syntax guidance or examples beyond the schema baseline, so 3 is appropriate.

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?

States a specific verb (Execute) and resource (ADB shell command on the Android device). Clearly distinct from siblings like android_tap or android_screenshot which target specific interactions rather than arbitrary shell execution.

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 on when to use this versus the many specialized sibling tools. An agent cannot tell whether to prefer android_shell for a task that a dedicated tool (e.g., android_list_apps, android_get_ui_tree) also covers.

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