podium-mcp

Overview Schema Source Related Servers Discussions Admin

orientation_set

Change an iOS simulator's screen orientation to portrait, landscape, or upside down via a Maestro flow. Requires the app's bundle identifier and device UDID.

Instructions

Sets the screen orientation on an iOS simulator via an ephemeral Maestro flow. bundleId is required (Maestro needs it for the appId flow header). Valid values: PORTRAIT, LANDSCAPE_LEFT, LANDSCAPE_RIGHT, UPSIDE_DOWN

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": {
      "udid": "<udid>",
      "bundleId": "<bundleId>",
      "value": "<value>"
    },
    "name": "orientation_set"
  }
}

Input Schema

Name	Required	Description
`udid`	Yes	Simulator / device UDID
`bundleId`	Yes	App bundle identifier
`value`	Yes	Target orientation: PORTRAIT \| LANDSCAPE_LEFT \| LANDSCAPE_RIGHT \| UPSIDE_DOWN
`timeoutMs`	No	Flow timeout in ms
`noLaunch`	No	Skip the implicit launchApp attach step (default false). Set true when an open modal or navigation state must not be disturbed.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.0Jun 23, 2026

TDQS

A4.2/5.0

Behavior3/5

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

No annotations; description mentions 'ephemeral Maestro flow' hinting at temporary change, but lacks detail on side effects, permissions, 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?

Two efficient sentences with no fluff, front-loading the action and adding key parameter detail.

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?

No output schema; description sufficiently covers purpose, parameters, and valid values for a simple setter tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema covers all 5 parameters; description adds context that bundleId is required for Maestro appId header, enhancing beyond schema descriptions.

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?

Description clearly states it sets screen orientation on an iOS simulator via Maestro flow, with explicit valid values. Distinguishes from sibling orientation_get.

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?

Implies usage context: set orientation vs get orientation from sibling. Does not explicitly state when-not or alternatives, but purpose is clear.

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