Skip to main content
Glama
babelwrap

io.github.soulfir/babelwrap-mcp

by babelwrap

babelwrap_scroll

Scroll web pages up or down by a specified amount or full viewport. Control direction, distance, and get a compact page snapshot.

Instructions

Scroll the page up or down.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
session_idYesThe active session ID.
directionNo"up" or "down" (default: "down").down
amountNo"page" (full viewport), "half" (half viewport), or pixel count as string (default: "page").page
compactNoIf True, return a compact snapshot with minimal whitespace.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior2/5

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

No annotations; description only mentions scrolling direction, not side effects like page boundary behavior or animations. Inadequate for a safe invocation.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Extremely short, but could include more context without being verbose. Balanced but not exemplary.

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?

Despite simple tool and output schema, description omits how parameters affect behavior (e.g., amount types). Incomplete for a full understanding.

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 has 100% coverage with descriptions; description adds no extra meaning beyond schema. 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?

Description clearly states verb 'Scroll' and resource 'page', and implies direction. However, it doesn't distinguish from other navigation tools like back/forward.

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?

No guidance on when to use this tool vs alternatives like babelwrap_back or babelwrap_navigate. Lacks usage context.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/babelwrap/babelwrap-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server