Skip to main content
Glama
Sign In
ios-agent-driver

ios-agent-driver

by CodeJonesW
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

deeplink

Open a URL or universal link in the iOS simulator to jump directly to a specific screen.

Instructions

Open a URL / universal link in the simulator (jump straight to a screen).

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

Input Schema

NameRequiredDescriptionDefault
urlYes
udidNoTarget simulator UDID. Defaults to the booted sim.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

No annotations provided, so description bears full burden. It describes the action but lacks details on side effects, prerequisites (e.g., simulator must be booted, implied by udid parameter), error handling, or whether it works only within an app or opens Safari. Adequate but not comprehensive.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Single sentence is concise and front-loaded with the action. No unnecessary words. However, could be structured to include a brief usage note or prerequisite without sacrificing conciseness.

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 simple tool with 2 params and no output schema, the description covers the basic purpose but omits important context like expected URL format, behavior when simulator is missing or URL is invalid, and what happens after opening (e.g., app changes). Enough for basic understanding but not fully complete for error-free 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 50% (only udid described). The tool description adds meaning to 'url' by stating it's a URL/link, but does not specify format or supported schemes. For 'udid', schema already describes it well; description adds nothing extra. Overall, compensates somewhat but could be more precise.

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?

Description clearly states 'Open a URL / universal link in the simulator', specifying a distinct action from sibling tools like 'launch' or 'tap'. The verb 'open' and resource 'URL/link' are specific and unambiguous.

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 versus alternatives, no when-not-to-use conditions, and no mention of prerequisites like booted simulator. The description only states what it does, not when to use it.

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