Skip to main content
Glama
Sign In
Xcode-Studio-MCP

Xcode-Studio-MCP

by kevinswint
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

simulator_type

Type text into focused input fields on the iOS Simulator to automate form entry and UI testing workflows.

Instructions

Type text into the currently focused field on the iOS Simulator. Requires idb (pip3 install fb-idb).

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": {
      "text": "<text>"
    },
    "name": "simulator_type"
  }
}

Input Schema

NameRequiredDescriptionDefault
simulator_udidNoSimulator UDID. Default: first booted simulator
textYesText to type

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior3/5

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

With no annotations provided, the description carries the full burden. It discloses the external idb dependency and implies statefulness ('currently focused field'), but omits error handling, idempotency, or timing behavior.

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?

Two sentences with zero waste: first states the action, second states the prerequisite. Information is front-loaded and appropriately scoped.

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 2-parameter tool with no output schema, covering the core action and dependency. However, gaps remain regarding failure modes (what if no field is focused?) and synchronous/asynchronous behavior.

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?

Input schema has 100% description coverage ('Simulator UDID', 'Text to type'), establishing baseline 3. The description adds no parameter-specific semantics beyond what the schema already provides.

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 the specific action ('Type text') and target ('currently focused field on the iOS Simulator'), distinguishing it from sibling tools like simulator_tap (gestures) and simulator_screenshot (visual capture).

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?

Provides critical prerequisite information ('Requires idb') but lacks explicit guidance on when to use this versus simulator_tap (e.g., 'use after focusing a field') or error conditions if no field is focused.

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