Skip to main content
Glama

android_type

Destructive

Types printable ASCII text into the focused field on an Android phone. Use it to enter search terms, messages, or form values without triggering Send or Enter.

Instructions

Type printable ASCII into the focused field. Hindi, emoji, newlines and literal %s are unsupported. Does not press Send or 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"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYes
deviceNoOptional connected device id, connection serial or exact model. Overrides the selected/default phone for this call.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.3

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare this as a non-read-only, destructive, non-idempotent, open-world operation, so the safety bar is partly met. The description adds genuinely useful behavior the annotations cannot convey: it does not submit (no Send/Enter), so a separate action is needed to commit text. It says nothing about append-vs-replace semantics at the cursor or failure behavior.

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, front-loaded with the core action, then the input constraint, then the submission caveat. Every sentence carries actionable information with no filler.

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 two-parameter tool with no output schema and full annotation coverage, the description supplies the essentials: target state (focused field), input limits, and the fact that it does not commit the text. Only minor gaps remain (cursor/append behavior, error mode).

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 50%: the 'device' parameter is documented in the schema while 'text' carries only a regex pattern. The description compensates by explaining the constraint in human terms — Hindi, emoji, newlines and literal %s are rejected — which lets an agent pre-validate input rather than discover the pattern failure at call time.

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 verb and target: 'Type printable ASCII into the focused field.' The ASCII-only scope and the note that it does not press Send/Enter implicitly separate it from android_key and android_tap, though no sibling is named explicitly.

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 implied by 'the focused field' (a field must already be focused, so tap first) and by the exclusion of Send/Enter (use android_key for those). However, no alternative tool is named and no explicit when-not guidance is given beyond unsupported character classes.

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