Skip to main content
Glama
Sign In
ios-control-mcp

ios-control-mcp

by als0m3
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

iphone_wifi_connections

Enable or disable network connections to a selected iPhone by running once while plugged in over USB, so the device can then be controlled wirelessly.

Instructions

Allow (or forbid) connecting to the selected device over the network. Run once while it is plugged in over USB.

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": "iphone_wifi_connections"
  }
}

Input Schema

NameRequiredDescriptionDefault
enabledNoDefault true.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A3.7/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It does disclose that this mutates a persistent device setting and requires a wired connection the first time, but it says nothing about whether the setting survives reboots, whether toggling off severs an active connection mid-session, or what errors occur without USB.

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?

Two sentences, front-loaded with the action and followed by the precondition; nothing is redundant or padded.

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 one-parameter toggle with no output schema this is nearly adequate, but the definition never explains how the target device is determined (presumably via iphone_list_devices) or how the new state can be verified afterward.

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% and the single boolean already carries 'Default true.', so the baseline is 3. The description adds the 'allow (or forbid)' mapping that corresponds to enabled=true/false, which is modest but real added 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?

States a specific action (allow or forbid network connections to the device) with a clear toggle semantic, which fits the name iphone_wifi_connections. It is not confused with the interaction siblings (tap, swipe, type), though it never explains how the 'selected device' is chosen.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives a concrete operational precondition: run once while the device is plugged in over USB. That tells an agent the correct setup context, but it never states the follow-on benefit (subsequent commands can run untethered) or what to do if no device is selected.

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