podium-mcp

by hoainho

Overview Schema Source Related Servers Discussions Admin

TypeScript

Local

open_url

Opens a URL, including deep-links and HTTPS, on a specified iOS simulator by providing the simulator UDID and the URL.

Instructions

Opens a URL on an iOS simulator (deep-links, https:// etc.).

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

Input Schema

Name	Required	Description	Default
`udid`	Yes	Simulator UDID
`url`	Yes	URL to open on the simulator

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.0Jun 23, 2026

TDQS

A3.5/5.0

Behavior3/5

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

No annotations provided, description carries full burden. Basic action is clear but lacks details on side effects, error handling, or prerequisites. Neither sufficient nor misleading.

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 sentence, front-loaded with key action and resource. No wasted words, efficient and clear.

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 simple tool with 2 parameters, but missing contextual info like prerequisite (device boot), return values, or failure modes. Not fully comprehensive.

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 covers both parameters (udid, url) with descriptions. Description adds no additional meaning beyond what the schema provides. Baseline score of 3 is appropriate.

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?

Clearly states the action (opens) and resource (URL on iOS simulator), with examples of URL types (deep-links, https). Distinguishes from siblings like webview_navigate which is for webviews in app.

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 explicit guidance on when to use this tool vs alternatives. Does not mention that the simulator must be booted first or that webview URLs may need webview_navigate instead.

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