Skip to main content
Glama

set_posture

Fold or unfold a foldable device using a preset or exact hinge angle, then return the settled posture, angle, and active screen.

Instructions

Fold or unfold a foldable device (form factor foldable in list_device_models — the iPhone Duo, Android foldables such as the Pixel 9 Pro Fold): a preset (closed, partial, open) or an exact hinge angle in degrees (angle 0-180) — pass exactly one. Reports the posture it settled in, the angle, and which screen is lit. Errors on a device without a hinge.

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": "set_posture"
  }
}

Input Schema

NameRequiredDescriptionDefault
angleNoExact hinge angle in whole degrees, 0 (shut) to 180 (flat open). Omit when passing a posture.
postureNoOne of 'closed', 'partial', 'open'. Omit when passing an angle.
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.1/5.0
Behavior4/5

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

The only annotation is readOnlyHint=false, so the description carries most of the burden and does so well: it discloses the exactly-one-of input contract, the post-condition ('reports the posture it settled in, the angle, and which screen is lit'), and the failure mode ('errors on a device without a hinge'). It stops short of saying whether state persists across sessions or how errors are surfaced.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence with the verb, device class, and input modes first, followed by the result and error behavior. Em-dash nesting makes it dense but every clause carries information; nothing is redundant.

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?

With no output schema, the description compensates by naming the return payload (settled posture, angle, lit screen), and all three parameters are documented. The main residual gap is the session-resolution precedence, which is only spelled out in the schema rather than the prose.

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%, so the schema already documents angle range, the posture enum, and session_id fallback behavior. The description restates the same semantics (presets closed/partial/open, 0-180 degrees) and adds only the cross-parameter exclusivity rule, so it sits at the baseline rather than adding substantially new meaning.

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 a specific verb and resource ('Fold or unfold a foldable device') plus the exact device class it applies to, gated on form factor `foldable` in list_device_models. An agent can tell this apart from rotate/shake-style siblings because it operates on a hinge with a preset or angle, and it explicitly fails on devices without a hinge.

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?

Gives clear preconditions and usage rules: only for foldable devices (pointing at list_device_models to verify), and 'pass exactly one' of posture or angle. It does not explicitly name a competing sibling (e.g., rotate) to route away from, which keeps it short of the top score.

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