Skip to main content
Glama
sidebutton

computer-use

by sidebutton

scroll

Scroll up, down, left, or right at a specified screen coordinate by a given number of clicks.

Instructions

Scroll in a direction by an amount at a coordinate.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
coordinateYes[x, y] in the model coordinate space (scaled to the screen).
scroll_directionYes
scroll_amountYesNumber of scroll 'clicks'.
Behavior2/5

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

Lacks details on effects of off-screen coordinates, scroll amount scaling, or side effects. Annotations absent, so description carries full burden but falls short.

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?

Single sentence is concise and front-loaded, but slightly too brief for a tool with three parameters.

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?

Complete for a trivial scroll action but omits crucial details like coordinate system, units, and limitations, leaving room for misuse.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage 67%; description adds no extra meaning. The scroll_direction enum lacks any explanation, and coordinate/scroll_amount descriptions are already in schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Description clearly states the action 'scroll' with direction, amount, and coordinate, distinguishing it from sibling mouse tools like click or move.

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 scroll versus alternatives like mouse_move or click-drag. No prerequisites or context provided.

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/sidebutton/plugin-computer-use'

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