Skip to main content
Glama

ios_status

Query iOS device status for Tailscale ports, pairing keys, WebDriverAgent readiness, and foreground app to confirm connectivity and control readiness.

Instructions

Query device status: Tailscale ports (62078/49152/8100), pairing keys, WDA readiness, and foreground app.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "ios_status"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior3/5

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

With no annotations supplied, the description must carry the full behavioral burden; the verb 'Query' signals a read operation and the field list tells the agent what surface is inspected, but it never states that the call is side-effect free, whether it is slow or blocking, or that it may return sensitive material like pairing keys. It adds real scope information but leaves the agent guessing on cost and safety.

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?

A single sentence with the resource up front followed by the enumerated checks; every token (including the three port numbers) adds information and nothing is repeated from the schema or title.

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

Completeness4/5

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

For a zero-argument read tool with an output schema present, the description covers the important unknown: which status dimensions are reported. Return structure is handled by the output schema, so the remaining omission is only the lack of guidance on when in a workflow to invoke it.

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 tool takes zero parameters, so there is nothing for the description to disambiguate and the baseline of 4 applies. The parenthetical port numbers are extra context about the returned data rather than parameter meaning.

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 ('Query') plus resource ('device status') and enumerates the concrete checks: Tailscale ports 62078/49152/8100, pairing keys, WDA readiness, and foreground app. That enumeration implicitly separates it from the action-oriented siblings like ios_tap or ios_launch_app, but it never names a sibling it should be preferred over, so it stops short of a 5.

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 read-only diagnostic nature is implied by 'Query' and the checklist of health signals, so an agent can infer this is the pre-flight/health-check tool. However, there is no explicit statement of when to call it (for example, before driving the UI) and no exclusion directing the agent elsewhere, such as to ios_lowlevel_telemetry for deeper signals.

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