Skip to main content
Glama
Sign In
simctl-mcp-server

simctl-mcp-server

by nzrsky
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

simctl_delete_device

Delete iOS simulator devices by UDID, device name, or remove all unavailable devices with a single command.

Instructions

Delete simulator devices.

Args: devices: List of device UDIDs, names, or 'unavailable' to delete all unavailable devices

Returns: Success message

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": {
      "devices": "<devices>"
    },
    "name": "simctl_delete_device"
  }
}

Input Schema

NameRequiredDescriptionDefault
devicesYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior2/5

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

With no annotations, the description must disclose behavioral traits. It mentions deleting devices and the special 'unavailable' value, but does not discuss irreversibility, permissions, or side effects. Limited transparency.

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?

Very concise, one-line purpose followed by parameter and return description. No wasted words, though slightly terse.

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

Completeness3/5

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

Given the simple tool with one parameter and output schema, the description covers the parameter's allowed values. However, it omits details like batching behavior or success message format. Adequate but could be more complete.

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

Parameters4/5

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

Schema coverage is 0%, so the description adds crucial meaning: it explains that the string array can contain UDIDs, names, or the keyword 'unavailable'. This is valuable beyond the bare schema.

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 clearly states 'Delete simulator devices', specifying the action and resource. It is distinct from sibling tools like simctl_boot_device or simctl_create_device, though it does not explicitly differentiate.

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 on when or when not to use this tool. No mention of alternatives or prerequisites. The description is purely operational without context.

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