Skip to main content
Glama
conorluddy

XC-MCP: XCode CLI wrapper

by conorluddy
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Local

simctl-get-details

Retrieve full simulator details from cached results to prevent token overload. Filter by device type, runtime, or availability for targeted drill-down into device lists.

Instructions

simctl-get-details

🔍 Get detailed simulator information from cached list results - Progressive disclosure for devices.

Retrieves on-demand access to full simulator and runtime lists that were cached during simctl-list execution. Implements progressive disclosure pattern: initial simctl-list responses return concise summaries to prevent token overflow, while this tool allows drilling down into full device lists, filtered by device type or runtime when needed.

Advantages

• Access full device lists without cluttering initial responses • Filter to specific device types (iPhone, iPad, etc.) • Filter to specific runtime versions • Get only available (booted) devices or all devices • Paginate results to manage token consumption

Parameters

Required

  • cacheId (string): Cache ID from simctl-list response

Optional

  • detailType (string): Type of details to retrieve

    • "full-list": Complete device and runtime information

    • "devices-only": Just device information

    • "runtimes-only": Just available runtimes

    • "available-only": Only booted devices

  • deviceType (string): Filter by device type (iPhone, iPad, etc.)

  • runtime (string): Filter by iOS runtime version

  • maxDevices (number): Maximum number of devices to return (default: 20)

Returns

  • Tool execution results with detailed simulator information

  • Complete device lists with full state and capabilities

  • Available devices and compatible runtimes

Related Tools

  • simctl-list: List available simulators and runtimes

  • xcodebuild-get-details: Get build or test details

Notes

  • Tool is auto-registered with MCP server

  • Requires valid cache ID from recent simctl-list

  • Cache IDs expire after 1 hour

  • Use for discovering available devices and runtimes

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cacheIdYes
detailTypeYes
deviceTypeNo
runtimeNo
maxDevicesNo

Tool Definition Quality

A4.5/5.0
Behavior4/5

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

With no annotations, the description discloses caching, cache ID expiration (1 hour), auto-registration, and return types. It lacks mention of permissions but is otherwise thorough for a read-only tool.

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 sections (advantages, parameters, returns, related tools, notes) but is somewhat verbose. Every sentence adds value, but some redundancy could be trimmed.

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?

Given no output schema, the description explains return values (full device lists, state, capabilities). It covers usage pattern, caching, filtering, and related tools, leaving no obvious gaps for an agent.

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 explains all 5 parameters: cacheId required, detailType with enum values, deviceType, runtime, and maxDevices with default. Each parameter's purpose and usage are clearly described.

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 the tool retrieves detailed simulator information from cached list results and implements progressive disclosure. This distinguishes it from sibling tools like simctl-list which returns concise summaries.

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 explains when to use this tool (after simctl-list) and provides advantages like filtering and pagination. It lists related tools but does not explicitly state when not to use or provide exclusions.

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