Skip to main content
Glama

ios_decision_run

Execute deterministic Decision API JSON step lists to automate iOS UI actions—launch apps, open URLs, tap, type, swipe, wait, and sleep—without a tethered Mac.

Instructions

Execute a deterministic Decision API JSON step list (launch, open_url, tap, tap_selector, wait_selector, swipe, type, button, sleep, reflex).

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": {
      "steps_json": "<steps_json>"
    },
    "name": "ios_decision_run"
  }
}

Input Schema

NameRequiredDescriptionDefault
steps_jsonYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. It discloses that execution is deterministic and lists the step types, but it does not describe side effects, permission requirements, error handling, atomicity, or whether steps run sequentially.

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 a single front-loaded sentence with no wasted wording. The parenthetical list of step types is dense but directly useful for understanding the tool's scope.

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?

An output schema exists, so return values need not be explained. However, for a tool whose only input is a JSON step list, the description omits the expected JSON structure and any execution semantics, leaving a meaningful gap for correct invocation.

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?

Schema description coverage is 0%, so the description must compensate for the single undocumented parameter. It adds meaning by identifying steps_json as a JSON step list and enumerating valid step types, but it does not specify the JSON structure or format expected for each step.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses a specific verb, "Execute," and names the resource as a "deterministic Decision API JSON step list," then enumerates supported step types. This clearly distinguishes it from single-action siblings like ios_tap or ios_swipe, though it does not explicitly name those alternatives.

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?

The phrase "step list" and the enumerated actions imply this tool is for multi-step automation sequences rather than one-off actions. However, there is no explicit guidance on when to use this versus individual sibling tools, nor any stated exclusions or prerequisites.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.