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

ios-control-mcp

by als0m3
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

iphone_type

Types text into the focused iPhone field, using the virtual keyboard for printable ASCII and the pasteboard for accents or emoji, then restores prior pasteboard text.

Instructions

Type text into the focused field. Printable ASCII is typed with a virtual keyboard; any other text (accents, emoji) is pasted through the device pasteboard, which is restored afterwards when it held text.

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": {
      "text": "<text>"
    },
    "name": "iphone_type"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses the dual-path implementation (virtual keyboard for printable ASCII, pasteboard paste otherwise) and the important side effect that the pasteboard is restored when it previously held text. It omits error behavior (e.g. no focused field) and latency, keeping it from a 5.

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 tight sentences with the core action front-loaded and the fallback/side-effect detail following. Every clause adds information; nothing is redundant.

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 one-parameter tool with no annotations and no output schema, the description covers the operation and its non-obvious side effects well. The remaining gaps are precondition/failure behavior and any return indication of success, which are modest for this tool's complexity.

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?

Schema coverage is 0% for the single 'text' parameter, but the description compensates by explaining how text content is handled differently by character class (ASCII vs accents/emoji), which is meaningful beyond the schema's type/min/max constraints. It does not mention the 1000-character limit or truncation behavior, but that constraint is already documented in the schema.

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?

States a specific verb and target: 'Type text into the focused field.' This is unmistakably distinct from the sibling tools (tap, swipe, button, open_app), and the word 'focused' scopes it to text-entry rather than navigation.

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?

Usage is only implied: an agent can infer it should call this for text entry after a field is focused, but the prerequisite (tap the field first) is never stated. There are no explicit exclusions or named alternatives, so the agent must infer the workflow.

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