Skip to main content
Glama

iphone_type

Types text into the currently focused iPhone text field; tap the field first to open the keyboard, then optionally press Return to submit.

Instructions

Type text into the text field that currently has keyboard focus.

Tap the field first (iphone_tap_text or iphone_tap) so the keyboard is open; without a focused field
the call fails. Text is appended at the cursor, not replacing existing content. Never use it for
passwords or passcodes – ask the user to enter those.

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
textYesText to type, exactly as it should appear. Use \n for a line break.
submitNotrue presses Return after typing (send a search, confirm a form).

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.2.0
    • addedInput schema / properties / submit / description
      Added value: +"true presses Return after typing (send a search, confirm a form)."
    • addedInput schema / properties / text / description
      Added value: +"Text to type, exactly as it should appear. Use \\n for a line break."
  2. First observedv0.1.0

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare non-read-only, non-destructive, open-world, non-idempotent behavior. The description adds genuinely new traits: text is appended at the cursor rather than replacing content, and the call fails without a focused field. The credential warning reinforces safety, though it stops short of describing what the tool returns (an output schema exists, so that is a minor gap).

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?

Three short sentences, each with a distinct job: what it does, what must precede it and why it fails, and how it modifies content, then the safety exclusion. The core action is front-loaded in the first sentence and nothing is repeated from the schema.

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

Completeness5/5

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

With an output schema present, annotations covering the safety profile, and 100% schema coverage, the remaining burden on the description is preconditions and side effects – both covered. Nothing an agent needs to invoke this correctly is missing.

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%, so both parameters (text, submit) are already fully documented, including the \n convention and the Return-key behavior. The description adds only the cursor-append semantics and does not touch the submit parameter, so it sits at the baseline for a fully documented 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 text field that currently has keyboard focus"), including the focus precondition. An agent can immediately tell this apart from iphone_tap or iphone_tap_text, which navigate rather than enter text.

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

Usage Guidelines5/5

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

Gives an explicit prerequisite ("Tap the field first (iphone_tap_text or iphone_tap) so the keyboard is open"), the failure condition without it ("without a focused field the call fails"), and an explicit exclusion ("Never use it for passwords or passcodes – ask the user to enter those"). When-to-use, when-not-to-use, and the alternative path are all present.

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