Skip to main content
Glama

ios_input_text

Types text into the currently focused field on an iOS or iPadOS device to fill forms and enter commands through automation.

Instructions

Type text into the currently focused field.

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

Input Schema

NameRequiredDescriptionDefault
textYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior2/5

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

With no annotations supplied, the description carries the full behavioral burden and does very little with it. It does not say whether text is appended or replaces existing content, what happens when no field is focused, whether the on-screen keyboard must be visible, or how special characters/unicode are handled.

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?

A single short sentence with the key constraint ('currently focused field') placed early and no redundant wording. It is efficient, though its brevity edges toward under-specification rather than optimal density.

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 tool with an output schema available, the description covers the core action, so nothing critical is wholly absent. It still omits the practical preconditions (focus state, keyboard visibility) and failure behavior that an agent committing to this call would want.

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?

There is one parameter and schema description coverage is 0%, so the schema supplies only the name 'text' and a string type. The description's 'Type text' maps trivially onto that parameter but adds no meaning about formatting, length, escaping, or submit behavior (e.g., trailing newline).

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 gives a specific verb ('Type') and target ('the currently focused field'), so an agent knows precisely what the tool does. It does not explicitly distinguish itself from near-neighbors like ios_key or ios_tap, leaving that differentiation to inference from the names.

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 through the phrase 'currently focused field', which hints that focus must be established first (e.g., via a tap), but the description never says so outright. There are no stated when-to-use/when-not conditions and no named alternative for key-press or element-targeted input.

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