Skip to main content
Glama
Sign In
simctl-mcp-server

simctl-mcp-server

by nzrsky
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

simctl_record_video

Record video from an iOS Simulator device. Configure codec, display, and output path for the recording.

Instructions

Start recording video of a simulator device.

Args: device: Device UDID, name, or 'booted' for current device output_path: Path where to save the video codec: Video codec (hevc, h264) display: Display to record (internal, external)

Returns: Recording start message

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": {
      "device": "<device>",
      "output_path": "<output_path>"
    },
    "name": "simctl_record_video"
  }
}

Input Schema

NameRequiredDescriptionDefault
deviceYes
output_pathYes
codecNohevc
displayNointernal

Output Schema

NameRequiredDescriptionDefault
resultYes

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 are provided, and the description does not disclose behavioral traits such as whether recording runs asynchronously, how to stop it, or any side effects. It only mentions a 'Recording start message' as return value.

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?

The description is highly concise: a single purpose sentence, an Args block, and a Returns line. No wasted words, and structure is front-loaded with key information.

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?

For a tool with 4 parameters, 2 required, and no output schema, the description explains all parameters but lacks guidance on how to stop recording, prerequisites (e.g., device must be booted), and handling of the recording process.

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%, but the description adds explanations for all parameters: device UDID/name/booted, output path, codec options (hevc, h264), and display options (internal, external). This adds 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 'Start recording video of a simulator device', specifying the verb 'record' and resource 'simulator device'. It distinguishes from sibling 'simctl_screenshot' which captures a still image.

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

Usage Guidelines2/5

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

The description provides no explicit guidance on when to use this tool versus alternatives like 'simctl_screenshot'. It does not mention prerequisites or context (e.g., device must be booted).

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