Skip to main content
Glama
Sign In
phonedriver

phonedriver

by hridaya423
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Rust
Local

scroll

Move the Android or iOS screen up, down, left, or right to reveal more content, or continue until specified text or an @ref appears.

Instructions

Scroll toward more content, or until the text or @ref in until shows.

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": {
      "direction": "<direction>"
    },
    "name": "scroll"
  }
}

Input Schema

NameRequiredDescriptionDefault
untilNoA text, `A|B` for either, or an @ref.
directionYesup, down, left or right.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.2

TDQS

B3.3/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full disclosure burden, and it omits the key behaviors: how far a single call scrolls, what happens if the `until` target never appears (error, timeout, success), and whether the response contains the revealed content. It only conveys the basic intent, leaving the agent to discover failure semantics empirically.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence with no wasted words, but 'toward more content' is slightly vague where a concrete statement about scrolling the viewport would be clearer.

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 two-parameter UI-automation tool with no annotations and no output schema, the definition covers intent but not outcome: it does not say whether scrolling reveals readable content directly or requires a subsequent `snapshot`, nor how a failed `until` condition is reported. Adequate to start a call, not to handle the result.

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 100%, so the baseline is 3. The description goes beyond the schema by explaining that `until` acts as a stop condition (scroll until that text or @ref appears), which the schema's terse 'A text, `A|B` for either, or an @ref' does not convey.

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 states a specific verb (scroll) and resource (content) and adds a bounded mode via `until`. It does not distinguish itself from the closely related `swipe` sibling, so it stops short of a 5.

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 `until` clause implies when to use the bounded mode ('or until the text or @ref shows'), which is useful context. It gives no guidance on when to scroll versus swipe, or on when to follow up with `screenshot`/`snapshot` to read the newly revealed content.

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

Deploy Server

Other Tools