Skip to main content
Glama
linux-computer-use-mcp

linux-computer-use-mcp

by dhakseshr

scroll

Move the mouse wheel by a given notch count in a selected direction, optionally after moving the pointer to x,y first.

Instructions

Scroll the mouse wheel by amount notches, optionally after moving to x,y first.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "direction": "<direction>"
    },
    "name": "scroll"
  }
}

Input Schema

NameRequiredDescriptionDefault
xNo
yNo
amountNo
directionYes
screenshotNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

B3.1/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden, yet it discloses only the optional pointer movement. It says nothing about what happens at scroll bounds, whether there is a delay/animation the caller must wait for, or what the default screenshot capture returns.

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 or redundancy. It is efficient, though its brevity is partly the cause of the missing parameter and behavior detail rather than pure economy.

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?

With five parameters, no annotations, no output schema, and zero schema description coverage, the definition should do more. Two parameters (direction, screenshot) and the return behavior go unexplained, leaving the agent to guess at the most basic required input.

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 description coverage is 0%, and the description only adds meaning for `amount` (interpreting it as notches) and `x`/`y` (move before scrolling). The required `direction` enum and the `screenshot` flag are left entirely to the schema titles, so coverage is partial.

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?

The description gives a specific verb and resource ("scroll the mouse wheel") plus the unit of movement (notches), and the optional move-to-x,y clause separates it from a pure move_mouse call. It is clear what the tool does, though it never contrasts itself with siblings like click or drag.

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?

Usage is implied rather than stated: the phrase "optionally after moving to x,y first" tells the agent it can combine positioning with scrolling, but there is no explicit when-to-use, when-not-to-use, or named alternative (e.g. scroll vs. press_key Page Down).

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