Skip to main content
Glama

adb_orientation

Read or change an Android device's screen orientation, including locking to portrait, landscape, reverse modes, or restoring auto-rotate.

Instructions

Get or set screen orientation. Can lock to portrait, landscape, reverse portrait, reverse landscape, or restore auto-rotate.

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": {
      "action": "<action>"
    },
    "name": "adb_orientation"
  }
}

Input Schema

NameRequiredDescriptionDefault
actionYes'get' to read current orientation, 'set' to change it
deviceNoDevice serial
orientationNoOrientation to set (required when action='set'): auto=sensor, portrait=0°, landscape=90°, reverse_portrait=180°, reverse_landscape=270°

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

B3.3/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 behavioral burden. It signals that 'set' mutates device state and that auto-rotate can be restored, but it omits key traits: whether the change persists across reboots or app restarts, whether special permissions or root are required, and what 'get' actually returns, none of which is covered by annotations.

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?

Two short sentences, zero filler, with the core verb/resource front-loaded and the available options following immediately. Every clause earns its place and nothing needs trimming.

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 3-parameter tool with no annotations and no output schema, the description is minimally adequate: it explains the get/set split and available orientations but not the return value of 'get' or side effects of 'set'. The schema covers parameters well, so the remaining gap is behavioral rather than structural.

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 both enums are documented in the schema, including the degree mapping (0°/90°/180°/270°) and the action semantics. The description only restates the orientation names (in spaced rather than snake_case form), so it adds no meaning beyond the schema; baseline 3 applies.

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 pair and resource ('Get or set screen orientation') and enumerates the supported orientations, so an agent immediately knows the tool's scope. It does not name or differentiate from siblings such as adb_screen or adb_screen_state, leaving ambiguity about which of the screen-related tools controls rotation versus power/state.

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 by noting it can lock or restore auto-rotate, which suggests a 'set' scenario, but it never states when to prefer this over adb_settings_put or adb_screen_state, nor does it state prerequisites like needing a connected device or a specific action selector. Usage is inferable from the action enum rather than from the description.

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