mcp-android-emulator

scroll_to_text

Scroll the Android screen until specified text becomes visible, using configurable direction and scroll limits.

Instructions

Scroll the screen until an element with specific text is visible

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

Input Schema

Name	Required	Description
`text`	Yes	Text to search for
`direction`	No	Scroll direction (default: down)
`maxScrolls`	No	Maximum scroll attempts (default: 10)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.0.0Aug 2, 2026

TDQS

A3.7/5.0

Behavior3/5

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

The description discloses the core behavior (scroll until visible) but omits important details such as what happens if the element is never found after max scrolls, whether it respects the 'direction' parameter, and any side effects. With no annotations, the description carries the full burden and falls short of full transparency.

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?

The description is a single, concise sentence that is front-loaded with the action and purpose. No unnecessary words or repetition.

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?

The tool has 3 parameters, no output schema, and no annotations. The description clearly explains the tool's goal but does not address what happens on success/failure, how direction and maxScrolls affect behavior, or return values. It is adequate for a simple scroll tool but lacks edge-case detail.

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?

The input schema already covers all parameters with descriptions (100% coverage), so the baseline is 3. The description does not add any additional meaning beyond the schema; it only restates the 'text' concept.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states a specific action (scroll) and resource (element with specific text), with a clear stopping condition (until visible). It distinguishes itself from the sibling 'scroll' tool, which presumably scrolls by offset, and from 'tap_text' which would tap rather than scroll.

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 description implies its use case: when you need to bring an element with specific text into view. However, it provides no explicit guidance on when to use this over alternative tools like 'scroll' or 'tap_text', nor any exclusions or prerequisites.

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