Manos MCP

Overview Schema Source Related Servers Discussions Admin

Set orientation

set_orientation

Changes the device orientation to portrait, landscape-left, landscape-right, or upside-down on Android to test app responsiveness to screen rotation.

Instructions

Set device orientation (portrait, landscape-left, landscape-right, upside-down). Android only; iOS simulators must be rotated via the Simulator menu.

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

Input Schema

Name	Required	Description	Default
`device_id`	Yes	Device id from list_devices (adb serial like 'emulator-5554', or an iOS simulator UDID)
`orientation`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.0Jul 31, 2026

TDQS

A4.2/5.0

Behavior4/5

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

With no annotations, the description carries the full burden. It discloses the Android-only platform limitation and lists all orientation options. It does not detail side effects or error conditions, but for a simple setter the core behavioral traits are adequately conveyed.

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, efficient sentence that leads with the action and resource, then lists the values and the platform caveat. Every word adds value, with no redundant phrasing.

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?

For a tool with only two parameters and no output schema, the description covers the essential aspects: what it does, acceptable values, and platform constraints. It could mention the effect on the device or return state, but the tool's simplicity makes the description largely complete.

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 schema already documents device_id with examples, and orientation has a self-explanatory enum. The description reinforces the allowed values and adds the Android-only context, but it does not provide significant additional parameter-level detail beyond the 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 clearly states the tool's function with a specific verb ('Set') and resource ('device orientation'), and enumerates the exact allowed values. This distinguishes it from sibling 'set_*' tools by focusing on orientation, and the platform note ('Android only') adds further specificity.

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

Usage Guidelines4/5

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

The description provides clear when-to-use guidance for Android devices and explicitly states an alternative for iOS simulators ('must be rotated via the Simulator menu'). While it doesn't contrast with other 'set_*' tools, the platform exclusion is a strong usage signal.

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