mcp-android-emulator

rotate_device

Rotate a connected Android device or emulator to portrait or landscape orientation.

Instructions

Rotate the device to portrait or landscape orientation

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": {
      "orientation": "<orientation>"
    },
    "name": "rotate_device"
  }
}

Input Schema

Name	Required	Description	Default
`orientation`	Yes	Target orientation

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.0.0Aug 2, 2026

TDQS

A3.5/5.0

Behavior2/5

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

With no annotations, the description carries the full burden for behavioral disclosure. It states the core action but omits any side effects, potential failure modes, or permission requirements. The description adds minimal context beyond the basic 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, concise sentence that is front-loaded with the action and includes the key parameter options. No wasted words.

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?

For a simple tool with one parameter and no output schema, the description is adequate but could benefit from noting behavioral aspects like whether the rotation is immediate, whether it triggers any side effects, or whether it fails on unsupported orientations.

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, with the parameter fully described ('Target orientation') and its enum values defined. The description merely restates the enum values ('portrait or landscape'), adding no new semantic detail, so the baseline of 3 applies.

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 (rotate) and resource (device), and clearly states the orientation options. It distinguishes itself from all sibling tools, none of which are rotation-related.

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 description implies usage context: use this tool when you need to change device orientation. However, it provides no explicit when-not-to-use guidance or references to alternative tools, though no direct alternatives exist among siblings.

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