Skip to main content
Glama
conorluddy

XC-MCP: XCode CLI wrapper

by conorluddy
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Rename Simulator

simctl-rename
Idempotent

Rename iOS simulator devices for clearer organization. Changes only the display name, preserving data and UDID.

Instructions

simctl-rename

Rename iOS simulator devices for better organization.

Overview

Changes the display name of a simulator without affecting its UDID or any data. Useful for organizing and identifying simulators with descriptive names. Quick operation completes instantly with no side effects.

Parameters

Required

  • deviceId (string): Device UDID to rename (from simctl-list)

  • newName (string): New display name for the simulator

Returns

Rename status showing old name, new name, confirmation that UDID is unchanged, success indicator, command output, and guidance emphasizing data preservation.

Examples

Rename simulator for clarity

await simctlRenameTool({
  deviceId: 'ABC-123-DEF',
  newName: 'Production Test Device'
});

Organize test devices

await simctlRenameTool({
  deviceId: 'TEST-UDID',
  newName: 'UI Tests - iPhone 16 Pro'
});

Related Tools

  • simctl-list: Find device UDID to rename

  • simctl-create: Create new simulator with specific name

  • simctl-clone: Clone simulator with new name

Notes

  • UDID remains unchanged - only display name is modified

  • All data and configuration preserved

  • Quick operation - completes instantly

  • New name must be unique - cannot duplicate existing names

  • Use descriptive names for better organization and identification

  • Perfect for organizing test devices by purpose or team

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
newNameYes
deviceIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv4.1.0

TDQS

A4.7/5.0
Behavior5/5

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

Beyond the annotations (idempotentHint, non-destructive), the description explicitly states that UDID remains unchanged, all data and configuration are preserved, and the operation completes instantly with no side effects. It also discloses a real constraint: 'New name must be unique - cannot duplicate existing names.' This significantly enriches the behavioral contract.

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-organized into Overview, Parameters, Returns, Examples, Related Tools, and Notes, making it easy to scan. However, it is a bit repetitive, with 'data preservation', 'no side effects', and 'quick operation' restated multiple times. The structure earns points, but some sentences could be trimmed without loss.

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?

Even without an output schema, the description discloses the return content (old name, new name, UDID unchanged, success indicator, command output, guidance) and all operating constraints. It also tells the agent where to source the deviceId and how the tool relates to siblings. This is sufficient for correct invocation in most simulated contexts.

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 must fully explain the parameters. It does: deviceId is described as 'Device UDID to rename (from simctl-list)' and newName as 'New display name for the simulator'. Two examples further clarify the usage, which compensates for the sparse schema.

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?

Description opens with a specific verb and resource: 'Rename iOS simulator devices', and states it 'Changes the display name of a simulator without affecting its UDID or any data.' It also distinguishes itself from related tools by listing simctl-list, simctl-create, and simctl-clone in the Related Tools section, so an agent can easily tell this tool apart from siblings.

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 gives clear context for when to use this tool: organizing and identifying simulators with descriptive names, and it notes that new names must be unique. It names related tools and suggests simctl-list for finding the UDID, but it does not explicitly state when not to use this tool or how to choose between rename, create, and clone in a direct comparison.

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