Skip to main content
Glama

scroll

Bring a selected element into view or shift the page by pixels to reveal off-screen content.

Instructions

Scroll an element into view, or scroll the page by a number of pixels.

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

Input Schema

NameRequiredDescriptionDefault
dyNoPixels down (negative scrolls up). Default one screen.
refNoElement ref from the latest snapshot, e.g. "e14".
tabNoTab handle from list_tabs, e.g. "chrome:812". Optional when only one tab is shared.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior2/5

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

With no annotations, the description carries the full burden and discloses almost nothing beyond the basic action. It does not say whether the call waits for the scroll to finish, what happens with an invalid or stale ref, whether scrolling is smooth or instant, or whether anything is returned.

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 filler that covers both modes efficiently. It is slightly under-specified rather than padded, and the two modes could be presented more distinctly, but nothing is wasted.

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

Completeness2/5

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

For an unannotated, no-output-schema browser automation tool with three optional parameters, the description omits the behavioral details an agent needs: ref staleness handling, tab resolution when multiple tabs exist, completion semantics, and failure behavior. All three parameters being optional also leaves the default state unexplained.

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 coverage is 100%, so dy (negative scrolls up, default one screen), ref (element ref from latest snapshot), and tab are already documented in the schema. The description adds only the high-level mapping of ref vs dy to the two modes, which the schema essentially already conveys.

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?

Names a specific verb-and-resource pair and covers both operating modes (element-into-view via ref, or page by pixel delta). An agent can distinguish it from siblings like click or hover, though no sibling is named 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?

The two-mode framing implies when each parameter applies (ref for element scrolling, dy for page scrolling), but there is no explicit when-to-use/when-not-to-use guidance and no mention of alternatives or prerequisites such as needing a fresh snapshot ref.

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