Skip to main content
Glama
conorluddy

XC-MCP: XCode CLI wrapper

by conorluddy

idb-targets

Discover, inspect, focus, and manage connections to IDB targets for iOS simulators and devices.

Instructions

idb-targets

Unified IDB target management - discover, inspect, focus, and manage connections.

Overview

Single tool for IDB target discovery and connection management. Routes to specialized handlers while maintaining clean operation semantics.

Operations

list

List all available IDB targets.

Parameters:

  • state (string, optional): Filter by state - 'Booted' or 'Shutdown'

  • type (string, optional): Filter by type - 'device' or 'simulator'

Example:

await idbTargetsToolUnified({
  operation: 'list',
  state: 'Booted'
})

Returns: List of targets with metadata, state, and type information.


describe

Get detailed information about a specific target.

Parameters:

  • udid (string): Target UDID

Example:

await idbTargetsToolUnified({
  operation: 'describe',
  udid: 'ABC-123-DEF'
})

Returns: Detailed target information including screen dimensions, device model, iOS version.


focus

Focus simulator window for interactive testing.

Parameters:

  • udid (string): Simulator UDID

Example:

await idbTargetsToolUnified({
  operation: 'focus',
  udid: 'ABC-123-DEF'
})

connect

Establish IDB companion connection to target.

Parameters:

  • udid (string, optional): Target UDID - auto-detects if omitted

Example:

await idbTargetsToolUnified({
  operation: 'connect',
  udid: 'ABC-123-DEF'
})

Notes: Establishes persistent gRPC connection for faster subsequent operations. Useful for warming up connections before automated testing.


disconnect

Close IDB companion connection to target.

Parameters:

  • udid (string, optional): Target UDID

Example:

await idbTargetsToolUnified({
  operation: 'disconnect',
  udid: 'ABC-123-DEF'
})

  • idb-app: App management on IDB targets

  • idb-ui-tap, idb-ui-input, idb-ui-gesture: UI automation on targets

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
operationYes
udidNo
stateNo
typeNo
Behavior4/5

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

No annotations exist, so the description carries the full burden. It explains behaviors for each operation: list returns a list, describe returns details, focus focuses a window, connect establishes a persistent connection, and disconnect closes it. Side effects like network usage are implied but not detailed, which is acceptable.

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, sections, and examples. It is somewhat lengthy but front-loads the overview and uses efficient formatting. The 'Related Tools' section is slightly extraneous but helpful.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the multiple operations, no output schema, and zero schema description coverage, the description covers parameters and return types broadly (e.g., 'List of targets with metadata'). However, it lacks detailed return structure or error handling, leaving some gaps.

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?

Schema description coverage is 0%, so the description must add meaning. It documents each parameter per operation (e.g., state and type for list, udid for describe/focus/connect/disconnect) and includes examples, adding significant value beyond the raw 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?

The description clearly states it is for 'Unified IDB target management' and lists operations (discover, inspect, focus, manage connections). The 'Related Tools' section distinguishes it from siblings like idb-app and idb-ui-tap, making the purpose unambiguous.

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?

Each operation is explained with context (e.g., connect: 'Establishes persistent gRPC connection... Useful for warming up connections'). The related tools section provides separation, but explicit when-not-to-use is missing, though implied.

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