Skip to main content
Glama
conorluddy

XC-MCP: XCode CLI wrapper

by conorluddy

Delete Simulator

simctl-delete
DestructiveIdempotent

Permanently delete iOS simulator devices to reclaim disk space. Requires shut-down device; deletion is irreversible.

Instructions

simctl-delete

Permanently delete iOS simulator devices.

Overview

Permanently removes a simulator device and all its data from the system. This action cannot be undone. The simulator must be shut down before deletion. Useful for cleaning up unused simulators to save disk space (simulators can be 5-10GB each).

Parameters

Required

  • deviceId (string): Device UDID to delete (from simctl-list)

Returns

Deletion status with device information, confirmation that action is permanent, success indicator, command output, and guidance emphasizing permanent nature of deletion.

Examples

Delete specific simulator

await simctlDeleteTool({ deviceId: 'ABC-123-DEF' });

Clean up old test device

await simctlDeleteTool({ deviceId: 'OLD-TEST-DEVICE-UDID' });
  • simctl-list: Find device UDID to delete

  • simctl-shutdown: Shutdown device before deletion (required)

  • simctl-create: Create new simulator after deletion

Notes

  • This action cannot be undone - device and all data permanently removed

  • Device must be shut down before deletion (safety check)

  • Simulators can be 5-10GB each - deletion frees significant disk space

  • Use simctl-erase instead if you want to keep device but reset state

  • Fast operation - completes in seconds

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
deviceIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv4.1.0

TDQS

A4.9/5.0
Behavior5/5

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

Beyond the destructiveHint and readOnlyHint annotations, the description emphasizes irreversibility, permanent data loss, the shutdown requirement, and disk-space impact. It adds meaningful operational context and does not contradict the annotations.

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

Conciseness4/5

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

The description is well-organized with headings, parameters, returns, examples, and related tools. It is slightly repetitive about the permanent nature of deletion, but this repetition is arguably useful for a destructive operation.

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

Completeness5/5

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

For a tool with a single parameter and no output schema, the description is complete: it covers prerequisites, return contents, alternatives, related tools, and operational effects. Nothing important is missing.

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

Parameters5/5

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

Schema coverage is 0%, so the description fully compensates: deviceId is explained as 'Device UDID to delete (from simctl-list)' and both examples show realistic values. This is sufficient for an agent to construct a correct invocation.

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 states a specific verb and resource: 'Permanently delete iOS simulator devices.' It further clarifies scope by noting all data is removed and explicitly contrasts with simctl-erase, so an agent can distinguish it from related simctl tools.

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

Usage Guidelines5/5

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

The description gives clear usage context: use for cleaning up unused simulators, requires the device to be shut down first, and identifies alternatives such as simctl-erase for resetting instead of deleting. It also points to simctl-list for finding the device and simctl-shutdown as a prerequisite.

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