Skip to main content
Glama
conorluddy

XC-MCP: XCode CLI wrapper

by conorluddy

simctl-list

List iOS simulators with intelligent caching and progressive disclosure. Returns concise summaries by default, preventing token overflow, with cache IDs for full details. Shows booted and recent devices first for faster workflows.

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-device: Boot, shutdown, or manage specific simulators

  • simctl-app: 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
deviceTypeNo
runtimeNo
availabilityNoavailable
outputFormatNojson
conciseNo
maxNo
Behavior5/5

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

No annotations exist, so description carries full burden. It comprehensively discloses caching (1-hour), progressive disclosure (concise vs full mode), device limiting (default max=5), token overflow prevention, sorting (booted/recent first), and smart filtering. No contradictions.

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?

Description is well-structured with sections (Overview, Parameters, Returns, Device Limiting, Examples, Related Tools, Notes). It is thorough but some may consider it slightly verbose. However, every section adds distinct value.

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?

No output schema, but description explains return in both modes (concise: summary with cacheId; full: limited device list with metadata). Covers all parameters, caching, sorting, and limits. Completely addresses the tool's complexity.

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 has 0% description coverage, but description fully explains all 6 parameters: deviceType (filter by type), runtime (filter by version), availability (with enum and default), outputFormat (enum), concise (toggle summary), max (limit in full mode). Also explains device limiting behavior.

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 clearly states it lists iOS simulators with progressive disclosure and caching. It distinguishes from siblings like simctl-get-details (retrieve full details via cache ID), simctl-device (manage simulators), and simctl-app (app operations). The verb 'List' and resource 'iOS simulators' are specific.

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

Usage Guidelines4/5

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

The description provides explicit alternatives (simctl-get-details, simctl-device, simctl-app) and notes 'Essential: Use this instead of 'xcrun simctl list''. Examples show typical use cases. It lacks explicit when-not-to-use but provides good context.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/conorluddy/xc-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server