Scroll a rented browser page horizontally or vertically to navigate content.
Scroll the rented browser page.
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": "browser-scroll"
}
}| Name | Required | Description | Default |
|---|---|---|---|
| x | No | Horizontal scroll delta | |
| y | No | Vertical scroll delta |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, and the description is minimal. It does not disclose behavioral details such as whether scrolling is relative to current position, whether it requires an active page, or any side effects. The description fails to add value beyond the bare minimum.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single sentence without unnecessary words. It is appropriate for the tool's simplicity, though it could be slightly more structured.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the tool's low complexity, the description and schema together are somewhat adequate. However, missing output schema and lack of behavioral details leave gaps about the effect of scrolling and coordinate system.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, with both parameters ('x' and 'y') described as 'Horizontal scroll delta' and 'Vertical scroll delta.' The description redundantly says 'scroll,' but adds no meaning beyond the schema. Baseline 3 is appropriate.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool's function: 'Scroll the rented browser page.' It uses a specific verb ('scroll') and resource ('rented browser page'), distinguishing it from sibling tools like browser-navigate or browser-click.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description provides no guidance on when to use this tool versus alternatives (e.g., browser-navigate, browser-click). No information about prerequisites, when not to use, or context is given.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.