podium-mcp

Overview Schema Source Related Servers Discussions Admin

swipe

Simulate a swipe gesture in a specified direction on an iOS simulator or device. Override start and end coordinates for precise placement.

Instructions

Swipes in a direction or between two coordinates via an ephemeral Maestro flow. direction is always required; startX/startY/endX/endY are optional overrides expressed as percentage strings (e.g. '10%,50%') or pixel values.

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": {
      "udid": "<udid>",
      "bundleId": "<bundleId>",
      "direction": "<direction>"
    },
    "name": "swipe"
  }
}

Input Schema

Name	Required	Description
`udid`	Yes	Simulator / device UDID
`bundleId`	Yes	App bundle identifier
`direction`	Yes	Swipe direction
`startX`	No	Start X (e.g. '10%' or '120')
`startY`	No	Start Y
`endX`	No	End X
`endY`	No	End Y
`timeoutMs`	No	Flow timeout in ms
`noLaunch`	No	Skip the implicit launchApp attach step (default false). Set true when an open modal or navigation state must not be disturbed.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.0Jun 23, 2026

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 lacks behavioral traits like destructiveness, authorization requirements, rate limits, or side effects. It only mentions the flow is 'ephemeral' but does not elaborate on behavior beyond the action itself.

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 extremely concise with two sentences. The first sentence states the action and mechanism, and the second details parameter requirements. No extraneous information, and important details are front-loaded.

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 absence of an output schema, the description does not explain return values or outcomes (e.g., success/failure). It also omits prerequisites beyond required parameters. The description covers the basic gesture but is incomplete for edge cases or error behavior.

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?

The schema has 100% parameter descriptions. The description adds value by clarifying that coordinate parameters are optional overrides and providing format examples (e.g., '10%,50%' or pixel values), enhancing understanding beyond the schema alone.

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 starts with the action 'Swipes in a direction or between two coordinates via an ephemeral Maestro flow,' which clearly identifies what the tool does and its mechanism. This distinguishes it from sibling tools like tap_on or press_key, which perform different gestures.

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 does not provide guidance on when to use this tool vs alternatives, such as tapping or scrolling. It mentions direction is required and coordinates are optional overrides, but does not specify appropriate scenarios or exclusions.

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