Skip to main content
Glama
conorluddy

XC-MCP: XCode CLI wrapper

by conorluddy
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Local

idb-app

Install, uninstall, launch, and terminate iOS apps on connected devices using IDB commands. Manage app lifecycle with a single tool.

Instructions

idb-app

Unified IDB app lifecycle management - install, uninstall, launch, terminate.

Overview

Single tool for IDB-based app management. Routes to specialized handlers while maintaining clean operation semantics.

Operations

install

Install iOS app via IDB.

Parameters:

  • appPath (string): Path to .app bundle

  • udid (string, optional): Target device UDID

Example:

await idbAppTool({
  operation: 'install',
  appPath: '/path/to/MyApp.app'
})

uninstall

Uninstall iOS app via IDB.

Parameters:

  • bundleId (string): App bundle ID

  • udid (string, optional): Target device UDID

Example:

await idbAppTool({
  operation: 'uninstall',
  bundleId: 'com.example.MyApp'
})

launch

Launch iOS app via IDB.

Parameters:

  • bundleId (string): App bundle ID

  • udid (string, optional): Target device UDID

  • arguments (string[], optional): Command-line arguments

  • environment (object, optional): Environment variables

  • streamOutput (boolean, optional): Stream app output

Example:

await idbAppTool({
  operation: 'launch',
  bundleId: 'com.example.MyApp',
  arguments: ['--debug'],
  streamOutput: true
})

terminate

Terminate running iOS app via IDB.

Parameters:

  • bundleId (string): App bundle ID

  • udid (string, optional): Target device UDID

Example:

await idbAppTool({
  operation: 'terminate',
  bundleId: 'com.example.MyApp'
})

Related Tools

  • idb-targets: List and manage IDB targets

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

  • simctl-app: Simctl-based app management

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
operationYes
udidNo
bundleIdNo
appPathNo
streamOutputNo
argumentsNo
environmentNo

Tool Definition Quality

A3.9/5.0
Behavior3/5

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

No annotations are provided, so the description carries full burden. It explains each operation's parameters and provides examples, but lacks details on side effects, permissions, error states, or what happens on failure.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is well-structured with headers, code blocks, and examples, but it is verbose. Some repetition could be reduced without losing clarity.

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 complexity (4 operations, 7 params), the description covers each operation's parameters and examples. However, it lacks any mention of return values or error handling, which would improve completeness.

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?

With 0% schema description coverage, the description adds significant value by documenting each operation's parameters and their meanings (e.g., appPath, bundleId, arguments, environment). Nested objects like 'environment' are explained clearly.

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 'Unified IDB app lifecycle management - install, uninstall, launch, terminate.' It specifies the verb and resource, and distinguishes from siblings like simctl-app explicitly mentioned in related tools.

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 'Related Tools' section lists alternatives (e.g., simctl-app, idb-ui-*), providing implicit guidance on when to use this tool. However, it doesn't explicitly state when not to use it, which would improve clarity.

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