Skip to main content
Glama
Sign In
mobilerun-mcp

mobilerun-mcp

by impeterwayne
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Press Home

press_home

Press the Home button on a connected device to return to the home screen, exit apps, or reset navigation.

Instructions

Press the Home button.

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

Input Schema

NameRequiredDescriptionDefault
deviceNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.4/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only states the action itself and does not mention whether a device must be specified, what side effects occur, or what the tool returns after pressing Home.

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

Conciseness3/5

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

The description is very short and action-first, with no filler words. However, it is terse to the point of omitting parameter and context details, making it concise but under-specified rather than well-structured and informative.

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

Completeness2/5

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

For a one-parameter tool with an output schema, the core action is stated, but the missing device parameter semantics, absence of usage guidance, and lack of behavioral notes leave an agent guessing about invocation context. The description is minimally adequate for a human but not complete for an agent navigating many UI-action siblings.

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

Parameters1/5

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

The input schema has one optional device parameter with no descriptions and 0% schema description coverage. The tool description never mentions the parameter, so it adds no meaning beyond the schema's name, type, and default value, and it fails to compensate for the low coverage.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description is a clear imperative sentence naming both the action ('press') and the target ('Home button'), so an agent can understand the tool's function. It does not explicitly differentiate itself from siblings like press_back or press_enter, but the specific Home target is unambiguous enough.

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

Usage Guidelines2/5

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

The description provides no guidance about when to use press_home versus alternatives such as press, press_back, or open_recent_apps. The only implied context is 'when you need to press Home,' with no exclusions or alternative routing.

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