Skip to main content
Glama
conorluddy

XC-MCP: XCode CLI wrapper

by conorluddy

List Simulators

simctl-list
Read-onlyIdempotent

List iOS simulators with concise summaries and caching to prevent token overflow. Filter by device type, runtime, and availability.

Instructions

simctl-list

List iOS simulators with intelligent progressive disclosure and caching.

Overview

Retrieves comprehensive simulator information including devices, runtimes, and device types. Returns concise summaries by default with cache IDs for progressive access to full details, preventing token overflow while maintaining complete functionality. Shows booted devices and recently used simulators first for faster workflows. Full output mode limits results to the most recently used devices for efficient browsing.

Parameters

Required

None - all parameters are optional

Optional

  • deviceType (string): Filter by device type (e.g., "iPhone", "iPad")

  • runtime (string): Filter by iOS runtime version (e.g., "17", "iOS 17.0")

  • availability (string, default: "available"): Filter by availability ("available", "unavailable", "all")

  • outputFormat (string, default: "json"): Output format ("json" or "text")

  • concise (boolean, default: true): Return concise summary with cache ID

  • max (number, default: 5): Maximum devices to return in full mode, sorted by lastUsed date (most recent first)

Returns

  • Concise mode: Summary with cacheId for detailed retrieval via simctl-get-details

  • Full mode: Limited device list (default 5 most recently used) with metadata showing total available and limit applied

Device Limiting in Full Mode

When concise: false, the response includes:

  • devices: Top N devices across all runtimes, sorted by lastUsed date (most recent first)

  • metadata: Shows total devices in cache, devices returned, and limit applied

  • Devices without lastUsed date are placed at the end

  • Total limit applies across all runtimes, not per-runtime

Examples

Get concise summary (default - prevents token overflow)

await simctlListTool({});

Get full list for iPhone devices (limited to 5 most recent)

await simctlListTool({
  deviceType: "iPhone",
  concise: false
});

Get full list with custom device limit

await simctlListTool({
  concise: false,
  max: 10
});

Filter by iOS version

await simctlListTool({ runtime: "17.0" });
  • simctl-get-details: Retrieve full device list using cache ID (bypasses max limit)

  • simctl-boot / simctl-shutdown: Boot, shutdown, or manage specific simulators

  • simctl-install / simctl-launch: Install and launch apps on simulators

Notes

  • Prevents token overflow (raw output = 10k+ tokens) via concise summaries and device limiting

  • Default max=5 limits output to ~2.5k tokens (90% reduction from full 50-device list)

  • 1-hour intelligent caching eliminates redundant queries

  • Shows booted devices and recently used simulators first in concise mode

  • Use simctl-get-details with cacheId for progressive access to full data (ignores max limit)

  • Device sorting: mostRecent (with lastUsed) → oldest (with lastUsed) → unknown (no lastUsed)

  • Smart filtering by device type, runtime, and availability

  • Essential: Use this instead of 'xcrun simctl list' for better performance

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
maxNo
conciseNo
runtimeNo
deviceTypeNo
availabilityNoavailable
outputFormatNojson

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changedv1.1.0
    • removedInput schema / additionalProperties
      Removed value: -false
    • removedInput schema / properties / availability / description
      Removed value: -"Filter by device availability"
    • removedInput schema / properties / concise / description
      Removed value: -"Return concise summary (true) or full list (false)"
    • removedInput schema / properties / deviceType / description
      Removed value: -"Filter by device type (iPhone, iPad, Apple Watch, Apple TV)"
    • addedInput schema / properties / max
      Added value: +{
      +  "default": 5,
      +  "type": "number"
      +}
    • removedInput schema / properties / outputFormat / description
      Removed value: -"Output format preference"
    • removedInput schema / properties / runtime / description
      Removed value: -"Filter by iOS runtime version (e.g., \"17\", \"iOS 17.0\", \"16.4\")"
  2. First observedv1.0.0

TDQS

A4.9/5.0
Behavior5/5

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

Annotations already declare readOnly, idempotent, and non-destructive behavior. The description adds substantial behavioral context beyond annotations: 1-hour caching, token-overflow prevention, default max=5, device sorting by lastUsed, metadata shape, and the cacheId handoff to simctl-get-details. No contradiction with 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-structured with headers, examples, and a related-tools section, and key facts are front-loaded. However, some information is repeated across Overview, Device Limiting, and Notes – e.g., token-overflow prevention, booted/recent sorting, and the cacheId workflow – so not every sentence earns its place.

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?

Despite no output schema, the description fully explains return behavior in both concise and full modes, the metadata fields, the limiting rule across runtimes, caching behavior, and includes multiple usage examples. It also routes to the correct sibling for full detail, making it complete for tool selection and invocation.

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 description coverage is 0%, so the description carries the full burden. It documents every parameter with type, default, and meaning, including non-obvious semantics like max applying only in full mode and sorting by lastUsed date. It also provides concrete filter examples for deviceType and runtime.

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 opens with a specific verb and resource: 'List iOS simulators'. It also distinguishes itself from the sibling tool simctl-get-details by explaining the concise-vs-full progressive disclosure model, so an agent can tell them apart immediately.

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 explicitly says when to use concise mode vs full mode, directs agents to simctl-get-details for full cached data, lists related tools for other operations, and even says to prefer this tool over 'xcrun simctl list'. This is explicit when-to-use guidance with alternatives.

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