Skip to main content
Glama
conorluddy

XC-MCP: XCode CLI wrapper

by conorluddy

simctl-health-check

Performs a complete diagnostic check of your iOS development environment, validating Xcode tools, simulators, runtimes, and disk space, returning actionable recommendations for any issues found.

Instructions

simctl-health-check

Comprehensive iOS simulator environment health check.

Overview

Performs a complete diagnostic check of your iOS development environment, validating Xcode tools, simulators, runtimes, and disk space. Returns actionable recommendations for any issues found. Checks 6 critical areas in seconds: Xcode Command Line Tools, simctl availability, available simulators, booted simulators, available runtimes, and disk space.

Parameters

None - performs complete environment check automatically.

Returns

Health report with pass/fail status for each check, specific guidance for failures, summary of passed/failed checks, and overall healthy status indicator.

Examples

Run complete health check

await simctlHealthCheckTool();

Check before CI/CD pipeline

// Validate environment before running test suite
const health = await simctlHealthCheckTool();
if (!health.healthy) {
  console.error('Environment issues detected');
}
  • simctl-list: See available simulators after health check passes

  • simctl-create: Create simulators if none found

  • simctl-suggest: Get intelligent simulator recommendations

Notes

  • Checks 6 critical areas: Xcode tools, simctl, simulators, booted devices, runtimes, disk space

  • Provides specific solutions for each failed check

  • Validates entire toolchain in seconds

  • Warns if disk usage over 80% (simulators require significant space)

  • Perfect for troubleshooting when operations fail unexpectedly

  • Use before CI/CD pipeline execution to ensure environment health

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior5/5

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

Since no annotations are provided, the description fully discloses the tool's behavior: it checks 6 areas, returns pass/fail status and actionable recommendations, warns about disk usage over 80%, and validates the entire toolchain in seconds.

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 headings, examples, and notes, but it is somewhat lengthy. However, each section adds value and the markdown formatting aids readability.

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?

The description is complete: it explains the purpose, what is checked, the output format, and provides usage examples. With no output schema, the description adequately covers what the agent can expect.

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?

The input schema has 0 parameters, so the baseline is 4. The description confirms no parameters are needed and explains that the tool performs a complete environment check automatically.

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 that the tool performs a 'comprehensive iOS simulator environment health check' and lists the 6 critical areas it checks. It distinguishes from sibling tools like simctl-list and simctl-create by focusing on diagnosis rather than listing or creating.

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 provides explicit guidance on when to use the tool, such as 'Perfect for troubleshooting when operations fail unexpectedly' and 'Use before CI/CD pipeline execution.' It also references related tools for follow-up actions.

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