Skip to main content
Glama

set_status_bar

Show a clean status bar (9:41, full battery and signal) for screenshots or restore the device's own status bar. The setting stays until changed or the session ends; iOS only.

Instructions

Show a clean status bar for screenshots (9:41, full battery, full Wi-Fi and cellular signal) or put the device's own status bar back. It stays until you change it or the session ends. iOS phones and tablets only.

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": {
      "preset": "<preset>"
    },
    "name": "set_status_bar"
  }
}

Input Schema

NameRequiredDescriptionDefault
presetYes'clean' for the screenshot status bar, 'default' for the device's own.
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.5/5.0
Behavior4/5

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

Beyond the readOnlyHint=false annotation, the description discloses the key stateful behavior: the status bar 'stays until you change it or the session ends,' and it explains how to revert via the default preset. It does not mention any device prerequisites (e.g., a booted simulator), which is a modest gap for a mutation tool.

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 short sentences, front-loaded with the operation and the visual result, then the persistence lifetime, then the platform restriction. Every clause carries information; nothing is redundant with the title or schema.

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 two-parameter, single-purpose toggle with a fully documented schema and no output schema, the description covers what it does, what the clean state contains, how to undo it, how long it lasts, and which platforms it supports. Nothing an agent needs in order to call it correctly is missing.

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 coverage is 100%, so the baseline is 3, but the description adds meaning by expanding what 'clean' actually entails (9:41, full battery, full signals) rather than merely restating the enum-free string parameter. The session_id target and fallback chain are left entirely to the schema, so it is not a full 5.

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 names the concrete operation (show a clean status bar or restore the device's own) and specifies exactly what the clean preset renders: 9:41, full battery, full Wi-Fi and cellular signal. It also scopes the tool with 'iOS phones and tablets only,' so an agent can tell whether this applies to the current device without opening the schema.

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?

Usage context is clear: the clean preset is 'for screenshots,' which tells the agent when to reach for it, and the iOS-only clause is an explicit exclusion for non-iOS devices. It stops short of naming a sibling alternative or stating what to do when the platform check fails, so it is strong but not fully prescriptive.

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