Skip to main content
Glama

app_scroll

Scroll a list or ScrollView in a live Expo app, targeting the first visible one or a specified element by ref, text, or testID. Report the updated screen after scrolling when needed.

Instructions

Scroll a list/ScrollView (first one on screen if no target).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "app_scroll"
  }
}

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)
amountNopixels, default ~70% of screen
testIDNotestID prop of the element
snapshotNoreport the screen afterwards (default true)
directionNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It usefully discloses the default targeting behavior, but says nothing about what happens when no scrollable element exists, whether direction defaults to down, or whether the resulting snapshot is captured automatically (that only appears in the schema).

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 waste; the parenthetical is compact though slightly cryptic in phrasing. Appropriate size for the amount of information conveyed.

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?

With seven optional parameters, no annotations, and no output schema, the description covers only the targeting default. It leaves the agent to infer failure modes and the direction/snapshot interplay, which the schema partially fills in but the description does not reinforce.

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 description coverage is 86%, so parameter meaning is already well documented. The description adds only the default-target nuance and nothing about direction values, amount defaults, or how ref/text/testID selectors interact.

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?

Description names a specific verb (scroll) and resource (list/ScrollView) and states the default target resolution rule (first one on screen if no target). It is clearly distinguishable from siblings like app_tap or app_snapshot, though it never names an alternative explicitly.

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 verb — use this when you need to move a scrollable container. There is no explicit when-to-use/when-not guidance, no mention of preconditions (e.g., a snapshot may be needed to target by ref), and no alternatives given.

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