Skip to main content
Glama

scroll_to

Scrolls a device UI until an element matching specified text becomes visible, enabling agents to locate off-screen controls and content.

Instructions

Scroll until an element matching the given text becomes 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"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYesCase-insensitive substring matched against an element's label, value, or accessibility id.
directionNoScroll direction in scrollbar semantics (up, down, left, right). Omit to auto-detect; required for horizontal searches.
session_idNoSession ID to target. Optional: falls back to the MCP-server-held dev_start session, then this project's `vibeview dev --detach` state, if either is available.
max_scrollsNoMax swipe attempts before giving up (default: 8).
element_typeNoiOS-only element type filter (Button, StaticText, TextField, SecureTextField, Cell, Image, Link, Switch, TextView, SearchField). Ignored on Android.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

The description conveys the key behavioral trait: this is an iterative scroll-and-search loop that stops on a match, implying a bounded retry cycle. With annotations covering only readOnlyHint=false, it does not say what happens when no match is found (error vs. silent return) or what is returned on success, and has no output schema to fill that gap.

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 zero filler. It is efficient, though its terseness leaves behavior and usage unstated rather than being genuinely complete.

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 5-parameter tool with no output schema, the description should address failure behavior and what a successful match yields. It covers only the loop condition, leaving the agent to infer outcomes when the element is never found.

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 100%, so every parameter including matching semantics, direction, session fallback, and max_scrolls is already documented. The description adds no parameter meaning beyond that, so the baseline 3 applies.

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) plus a precise termination condition (until an element matching the given text becomes visible), which cleanly separates it from plain 'scroll' or 'swipe'. It does not name a sibling explicitly, 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 Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no guidance on when to prefer this over 'find', 'scroll', or 'swipe'. The only conditional advice ('omit direction to auto-detect; required for horizontal searches') lives in the schema, not the description.

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