Skip to main content
Glama

rotate

Change the orientation of a live cloud device during a session—portrait to landscape or supported degree turns—and return the new orientation for verification.

Instructions

Rotate the device. A phone (and an Android foldable) toggles between portrait and landscape; the iPhone Duo turns a quarter clockwise, or by degrees 180/270. Reports the new orientation. Not available on TV devices.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "rotate"
  }
}

Input Schema

NameRequiredDescriptionDefault
degreesNoiPhone Duo only: 90 (default, a quarter turn clockwise), 180, or 270 (a quarter turn back). Other devices accept only 90.
session_idNoSession ID to target. Optional: falls back to the MCP-server-held dev_start session, then this project's `vibeview dev --detach` state, if either is available.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.3/5.0
Behavior4/5

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

Annotations declare readOnlyHint=false, and the description adds useful behavioral context beyond that: device-dependent rotation semantics, that it reports the new orientation, and that it is unavailable on TV devices. It stops short of detailing side effects or failure modes.

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?

Three tightly written sentences with no wasted wording; device-specific behavior and the TV exclusion are front-loaded and easy to scan.

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

Completeness5/5

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

For a simple rotation tool with no output schema and full schema coverage, the description supplies everything an agent needs: device applicability, degree behavior, the fact that the new orientation is reported, and an explicit platform exclusion.

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%, so both parameters are fully documented. The description reinforces the degrees semantics for iPhone Duo versus other devices but largely restates what the schema already says, so baseline 3 is appropriate.

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?

States the specific verb 'rotate' and resource 'the device,' then immediately differentiates behavior by device type: toggling on phones and Android foldables, quarter-turn or specified degrees on iPhone Duo. This clearly distinguishes it from siblings like set_posture.

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?

Provides clear applicability context, including device-specific rotation behavior and an explicit exclusion ('Not available on TV devices'), but does not name alternative tools such as set_posture when rotation is not appropriate.

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