podium-mcp

by hoainho

Overview Schema Source Related Servers Discussions Admin

TypeScript

Local

app_launch

Launch an app on an iOS simulator using its bundle identifier. Specify the simulator UDID and app bundle ID.

Instructions

Launches an app on an iOS simulator by bundle ID.

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>"
    },
    "name": "app_launch"
  }
}

Input Schema

Name	Required	Description	Default
`udid`	Yes	Simulator UDID
`bundleId`	Yes	App bundle identifier (e.g. com.example.MyApp)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.0Jun 23, 2026

TDQS

B3.2/5.0

Behavior2/5

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

No annotations provided, so description carries full burden. It fails to disclose side effects (e.g., does it reset app state?), prerequisites (simulator must be booted), or error conditions (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, well-structured sentence. No unnecessary words or repetition. Efficiently conveys core function.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Despite low parameter complexity and no output schema, the description lacks important context for an action tool: prerequisites (simulator booted, app installed), potential errors, and behavior when conditions aren't met.

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 100%, so baseline 3. The description adds no extra meaning beyond what the schema already provides for 'udid' and 'bundleId'.

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 action (launch), target (app on iOS simulator), and key parameter (bundle ID). It distinguishes from sibling tools like app_install or app_terminate.

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?

No guidance on when to use this tool vs alternatives (e.g., app_install if app not installed, or device_boot if simulator not running). No prerequisites mentioned.

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