Skip to main content
Glama

android_type_text

Types ASCII or Unicode text into the focused Android input field, with an option to send Enter afterward. Use it to fill forms, search boxes, or chat inputs during Android automation.

Instructions

Types ASCII or Unicode text into the focused Android input field with optional press_enter.

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

Input Schema

NameRequiredDescriptionDefault
textYesText to type.
press_enterNoSend ENTER keyevent after typing.
device_serialNoOptional ADB device serial. Defaults to the first connected device.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It discloses the focused-field precondition and Unicode support, which is useful, but says nothing about whether existing text is replaced or appended, what happens when no field is focused, or how failures are reported.

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 front-loaded sentence with no filler; the core action and the optional flag are stated immediately with zero redundancy.

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 three-parameter tool with full schema coverage and no output schema, the definition covers the essentials, but with no annotations it should also address preconditions and failure behavior to be complete.

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 all three parameters are already documented in the schema; the description only restates press_enter as optional. The one small addition is that the text parameter accepts both ASCII and Unicode, but no formatting or escaping rules are given.

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 names a specific verb and target: typing ASCII or Unicode text into the focused Android input field. That is clearly distinct from sibling operations like android_keyevent or android_tap_element, though it never explicitly contrasts itself with them.

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 phrase 'focused Android input field' implicitly states the prerequisite that a field must already have focus, which hints at when the tool applies. However, there is no explicit guidance on what to call first (e.g., a tap/focus tool) or when to prefer android_keyevent instead.

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