MCP Mobile Server

ios_shutdown_simulator

Shuts down iOS simulators to free system resources and manage virtual devices during mobile development testing workflows.

Instructions

Shutdown an iOS simulator

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": {
      "udid": "<udid>"
    },
    "name": "ios_shutdown_simulator"
  }
}

Input Schema

Name	Required	Description	Default
`udid`	Yes	Simulator UDID

Schema Changelog

Changes observed during successful MCP inspections.

First observedDec 7, 2025

TDQS

C2.9/5.0

Behavior2/5

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

With no annotations provided, the description carries full burden but only states the action without behavioral details. It doesn't disclose if shutdown is destructive, requires specific simulator states, has side effects, or what happens on success/failure, leaving significant gaps 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?

The description is a single, direct sentence with no wasted words, making it highly concise and front-loaded. Every word contributes to stating the tool's purpose efficiently.

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?

Given the tool's complexity (a mutation with no annotations and no output schema), the description is incomplete. It lacks details on behavioral traits, usage context, and expected outcomes, failing to provide enough information for safe and effective use by an AI agent.

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 description coverage is 100% with the parameter 'udid' documented as 'Simulator UDID', so the schema provides complete parameter info. The description adds no additional meaning beyond the schema, resulting in a baseline score of 3 as it doesn't compensate but schema is sufficient.

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 'Shutdown an iOS simulator' clearly states the action (shutdown) and target resource (iOS simulator), which is specific and unambiguous. However, it doesn't differentiate from sibling tools like 'android_stop_emulator' or 'ios_boot_simulator' beyond the iOS platform mention, missing explicit sibling distinction.

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?

No guidance is provided on when to use this tool versus alternatives like 'android_stop_emulator' or 'ios_boot_simulator', nor does it mention prerequisites such as needing a booted simulator. The description only states what it does without context for selection.

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