Skip to main content
Glama
Sign In
chrome-fast

chrome-fast

by ventos312
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

scroll

Moves the page up or down by a set pixel amount, or brings a specified element into view.

Instructions

Scroll the page by an amount, or scroll an element into view.

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
amountNoPixels to scroll when no selector is given (default: 500)
selectorNoElement to scroll into view; omit to scroll the page: a ref number from get_page/navigate (e.g. "3") or a CSS selector
directionNoScroll direction when no selector is given (default: down)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.3.0

TDQS

B3.2/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full disclosure burden. It never says whether the scroll is animated or instant, whether the call waits for lazy-loaded content, whether it is safe/non-destructive, or what state is returned afterwards — all relevant for a UI-affecting action.

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 compact sentence with the primary action front-loaded and no filler. The 'or' construction is slightly terse but reads cleanly.

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 three-optional-parameter UI tool with no annotations and no output schema, the description covers the available modes but omits post-scroll behavior, waiting semantics, and any hint about what the agent can do next, leaving meaningful gaps.

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 defaults (500px, down) and the ref-vs-CSS-selector distinction are already documented in the schema. The description only restates the mode split and adds no format or precedence detail beyond it, which matches the baseline for full coverage.

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 its two distinct modes (page by amount, or element into view), which is enough to tell it apart from siblings like click, navigate, or screenshot. It stops short of naming siblings or scoping when each mode applies.

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 modes are implied by the description, and the selector's schema text hints that refs come from get_page/navigate, but the description itself gives no explicit when-to-use guidance, no prerequisites, and no mention of alternatives such as using click or evaluate instead.

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

Deploy Server

Other Tools