Skip to main content
Glama
Sign In
android-emulator

android-emulator

by Sajinthan
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

clear_status_bar

Restore the real Android status bar by exiting demo mode, removing fake overlays to return to the normal device state.

Instructions

Exit demo mode and restore the real status bar

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

Input Schema

NameRequiredDescriptionDefault
serialNoDevice serial (e.g. emulator-5554). Optional when exactly one device is connected.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.8/5.0
Behavior3/5

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

With no annotations, the description carries the full burden of behavioral disclosure. It does state the core effect (exiting demo mode and restoring the real status bar), but it does not mention idempotency, whether all demo customizations are cleared, or what happens if the device is not in demo mode.

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 one short sentence with no filler. The main action is front-loaded and every word contributes to understanding what the tool does.

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 simple state-reset tool with one optional parameter and no output schema, the description plus the schema cover most of what an agent needs. It is slightly incomplete only in not explicitly connecting this tool to set_status_bar as its counterpart, though the sibling list supplies that context.

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 input schema already documents the only parameter, serial, with 100% coverage, including the optional-when-one-device rule. The description adds no parameter-level detail, so the baseline score of 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?

The description uses a specific verb ('exit'), names the resource ('demo mode'), and states the outcome ('restore the real status bar'). This clearly separates it from the sibling set_status_bar by signaling it is a reversal/reset action rather than a set action.

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

Usage Guidelines3/5

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

The phrase 'exit demo mode' implies the tool should be used when the device is in demo mode and the real status bar is needed. However, it does not explicitly state when not to use it or mention set_status_bar as the counterpart for entering demo mode.

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

Deploy Server

Other Tools