Skip to main content
Glama
Sign In
rn-device-mcp

rn-device-mcp

by Artem-Pavlenko
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Open the RN dev menu

android_dev_menu

Sends the Android menu key to open the React Native dev menu in debug builds, with optional device selection by adb serial.

Instructions

Sends the menu key, which opens the React Native dev menu in debug builds.

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

Input Schema

NameRequiredDescriptionDefault
serialNoadb serial (from android_devices). Default: the only online device.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare it is not read-only and not destructive, so the safety question is answered. The description adds real value beyond that by disclosing the underlying mechanism (a menu key press) and the debug-build prerequisite, which explains why it may appear to do nothing on a release build.

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?

A single tight sentence that leads with the action and immediately explains the effect. No filler, no restatement of the title or name.

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 one-optional-parameter action with no output schema, the definition is nearly complete: mechanism, effect, and the debug-build constraint are all covered. Only the behavior on non-debug builds (silent no-op vs. error) is left unstated.

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 coverage is 100% and the single serial parameter already documents its default ("the only online device") and its source tool (android_devices). The description adds nothing about the parameter, so the baseline 3 applies.

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?

Names a specific mechanism and outcome ("Sends the menu key, which opens the React Native dev menu"), so the agent knows exactly what the side effect will be. It does not explicitly distinguish itself from android_input, which could also emit keyevents, leaving a small ambiguity for a model choosing between them.

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 "in debug builds" gives an implied precondition for when this works, which is useful. However, there is no explicit when-to-use guidance and no mention of the alternative (android_input) for non-debug builds or for dismissing the menu.

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