Skip to main content
Glama

phone_type

Types text into Android input fields without keyboard tapping; target an element or the focused field and optionally press Enter to submit.

Instructions

Type text into an input (no keyboard tapping needed). Without target it types into the focused input. submit presses Enter/Search/Send afterwards.

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

Input Schema

NameRequiredDescriptionDefault
textYes
afterNoreturn the updated element list afterwards (default true)
appendNokeep existing text (default replaces it)
settleNomax ms to wait for the screen to stop changing before reading it (default 2500)
submitNopress Enter afterwards
targetNoinput to type into: what to act on: element number from the last screen ("12"), grid cell ("C7"), pixel coordinates ("540,1200") or visible text ("Sign in"; text missing from the element list is found by OCR)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It usefully discloses the focused-input fallback and the post-typing Enter behavior, but says nothing about failure modes, whether an unfound target errors out, or how long the action blocks beyond the schema's settle field.

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 short sentences, front-loaded with the primary action and followed by the default-behavior caveat. Nothing is redundant or padded.

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 six-parameter input tool with no annotations and no output schema, the description covers the core action and the two most consequential behaviors (focus fallback, submit). The remaining optional parameters are adequately handled by the schema's own descriptions, so little 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 coverage is 83%, so the schema already documents most parameters and the baseline is 3. The description adds modest meaning beyond it: the no-target focus fallback and the fact that submit may trigger Enter/Search/Send rather than only Enter, but append, after, and settle are left entirely to the schema.

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 uses a specific verb and resource: 'Type text into an input', with the parenthetical 'no keyboard tapping needed' implicitly distinguishing it from the key-tapping sibling phone_key. The purpose is unmistakable, though it never names an alternative tool outright.

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

Usage Guidelines4/5

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

It gives clear operating context: with no target it types into whatever input currently has focus, and submit presses Enter/Search/Send afterwards. It does not state exclusions or explicitly route to phone_key or phone_tap when typing is not appropriate, so it falls short of a 5.

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