Skip to main content
Glama
Sign In
ios-agent-driver

ios-agent-driver

by CodeJonesW
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

launch

Launch an installed iOS app in a simulator by specifying its bundle ID. Returns the process ID of the launched app.

Instructions

Launch an installed app by bundle id. Returns the launch output (pid).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "bundle_id": "<bundle_id>"
    },
    "name": "launch"
  }
}

Input Schema

NameRequiredDescriptionDefault
bundle_idYes
udidNoTarget simulator UDID. Defaults to the booted sim.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior2/5

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

No annotations provided, so description must cover behavior. It mentions returning the pid but omits side effects (e.g., app entering foreground, state changes) and error conditions (e.g., app not found).

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

Conciseness5/5

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

Single sentence, front-loaded with action and resource, no wasted words. Efficient and clear.

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?

Adequate for a simple tool with two parameters, but lacks context on preconditions (e.g., simulator must be booted, app must be installed) and failure modes. Output schema is absent, but return value is mentioned.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Description adds minimal extra meaning beyond schema: 'bundle id' is identified as app identifier. The udid's default behavior is explained. With only 50% schema coverage, the description partially compensates but does not fully detail parameter constraints.

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?

Clearly states the action ('launch'), resource ('installed app by bundle id'), and output ('pid'). Distinguishes from siblings like 'install_app' and 'deeplink' by specifying the launch mechanism.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Implies the app must be installed first but does not explicitly guide when to use this tool versus alternatives. No mention of prerequisites like a booted simulator.

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