Skip to main content
Glama

phone_scroll

Scrolls the Android screen or a specified scrollable element in a chosen direction to reveal off-screen content.

Instructions

Scroll the screen or one scrollable element. direction is where the content moves into view: "down" shows what is below.

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

Input Schema

NameRequiredDescriptionDefault
afterNoreturn the updated element list afterwards (default true)
amountNofraction of the area to scroll (default 0.6)
settleNomax ms to wait for the screen to stop changing before reading it (default 2500)
targetNoscrollable element to scroll (default: the main scrollable area)
directionYes

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?

With no annotations supplied, the description carries the full burden and only partly meets it. It usefully clarifies what 'direction' means behaviorally ('down' shows what is below), but says nothing about side effects — whether scrolling loads new content, whether the view resets, or what the response contains after a scroll.

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 with zero filler; the core action is front-loaded and the direction clarification follows immediately. Nothing is wasted or buried.

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 five-parameter interaction tool with no annotations and no output schema, the description covers the action and the trickiest parameter but omits what scrolling does to page state or what gets returned. Adequate to invoke, thin for predicting behavior.

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 80%, so the baseline is 3, and the description adds real value by defining the semantics of the direction enum in terms of content movement into view, which the bare enum values do not convey. It does not extend to amount, settle, target, or after, but those are documented in 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?

States a specific verb ('Scroll') and resource ('the screen or one scrollable element'), which is unambiguous. It stops short of differentiating itself from the sibling phone_swipe, which could plausibly be used for the same goal.

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 purpose: scroll when content lies outside the viewport. There is no explicit when-to-use or when-not guidance, and no alternative (e.g. phone_swipe) is named as the tool to prefer in a related situation.

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