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

rn-device-mcp

by Artem-Pavlenko
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Shut down a simulator

ios_shutdown

Shut down the booted iOS Simulator or a specified simulator by UDID or name to free resources and reset device state.

Instructions

Shuts down the booted simulator (or the given one).

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

Input Schema

NameRequiredDescriptionDefault
deviceNoSimulator udid or name. Default "booted" (the running simulator).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false and destructiveHint=false, so safety is largely covered. The description adds no consequence detail — it does not say that running apps are terminated or that simulator state is lost, which matters for a shutdown. The shutdown is reversible via boot, so this is a gap rather than a contradiction with destructiveHint=false.

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?

One short, front-loaded sentence with zero padding. The default behaviour is expressed in a parenthetical without burying the verb.

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 single-optional-parameter, non-read-only tool with full schema coverage and annotations, the description is nearly sufficient. Only the consequence of shutting down (terminated apps, lost runtime state) and behaviour with no booted device are missing.

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 optional device parameter is fully documented in the schema, including the "booted" default. The description's parenthetical "(or the given one)" only restates that optionality, adding no new meaning such as name-vs-udid acceptance.

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?

States a specific verb and resource ("Shuts down the ... simulator") plus the scope nuance that the target defaults to whatever is booted. That is enough to distinguish it from ios_boot and ios_simulators, though neither sibling is named explicitly.

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?

Usage is implied: shut down the running simulator or a named one. There is no explicit guidance on when not to use it, no mention of the inverse ios_boot, and no note about what happens when no simulator is booted.

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