Skip to main content
Glama

app_type

Sets text in an app input field by ref, testID, or placeholder, replacing existing content by default and optionally appending or submitting.

Instructions

Set text in an input (replaces by default). Target by ref, testID, or placeholder text.

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": {
      "value": "<value>"
    },
    "name": "app_type"
  }
}

Input Schema

NameRequiredDescriptionDefault
refNoref from the last snapshot, e.g. "e4"
fullNofull screen instead of a diff
textNovisible label/placeholder (exact match first, then contains)
valueYes
appendNo
submitNofire onSubmitEditing (like pressing enter)
testIDNotestID prop of the element
snapshotNoreport the screen afterwards (default true)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are supplied, so the description must carry the behavioral load. It usefully discloses that text replacement is the default rather than appending, which the schema does not say, but omits focus requirements, failure behavior for ambiguous or missing selectors, and whether the resulting screen snapshot is the return value.

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, zero filler, with the core action and its default behavior front-loaded before the targeting options.

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 an eight-parameter input tool with no annotations and no output schema, the definition covers the essentials: what it writes, the default replace mode, and how to target. Gaps around prerequisites and failure modes are modest given the schema documents most optional flags.

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 75%, so most parameters are already documented, including submit (onSubmitEditing) and snapshot. The description's main contribution beyond the schema is the replace-by-default meaning of append; it says nothing extra about the required value parameter or how text matching resolves when several elements match.

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?

"Set text in an input" is a specific verb+resource that an agent can distinguish from app_tap or app_scroll without opening a schema. It adds the default replace semantics and the three targeting strategies, though it never names a sibling or explicitly rules one out.

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?

"Target by ref, testID, or placeholder text" implies which selector to supply, and "replaces by default" hints that append is the alternative. There is no explicit when-to-use guidance versus app_tap for focusing a field first, nor any stated prerequisite such as the input being mounted or visible.

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