Skip to main content
Glama

scroll

Move the current view up, down, left, or right on a live device using gesture presets, so agents can navigate UI when elements are off-screen.

Instructions

Scroll the current view up, down, left, or right using a gesture preset.

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

Input Schema

NameRequiredDescriptionDefault
nameYesScroll direction: up, down, left, or right (sent as gesture_preset "scroll_<direction>").
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.

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?

The only annotation is readOnlyHint=false, so the agent learns nothing about effect scope from the metadata. The description adds that the scroll is dispatched as a gesture preset, which explains the mechanism, but it omits scroll distance, whether the view is bounded, and what the call reports back.

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?

A single well-formed sentence that front-loads the verb-resource pair and enumerates the valid directions without any padding.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a two-parameter UI gesture tool with no output schema and fully documented parameters, the definition covers what an agent needs to invoke it. The remaining gap is behavioral (how far it scrolls, what happens at view boundaries), which is minor at this complexity.

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%, with both the direction values and the session_id fallback chain fully documented in the schema. The description echoes the same four directions without adding syntax or behavioral detail, 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 gives a specific verb (scroll) and resource (current view) plus the four supported directions, which distinguishes it reasonably from scroll_to by emphasizing the current view rather than an element target. It never names the sibling explicitly, so the differentiation is implied rather than stated.

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 only implied: 'current view' hints at free scrolling as opposed to scrolling to a specific element, but the description never says when to prefer this over scroll_to or swipe, nor does it mention any preconditions such as an active session.

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