Skip to main content
Glama
Sign In
SapperMCP

SapperMCP

by MasterX1582
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Scroll Mouse

scroll_mouse

Scroll the mouse wheel up or down, optionally at specific X11 coordinates, to automate desktop navigation.

Instructions

Scroll the mouse wheel up/down, optionally at coordinates. X11 only.

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_mouse"
  }
}

Input Schema

NameRequiredDescriptionDefault
xNo
yNo
clicksNo
directionNodown

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full behavioral burden. It usefully discloses the platform restriction (X11 only) and that coordinate targeting is optional, but says nothing about what happens if x/y are omitted (presumably current pointer position) or what the side effects/response look like on a failed scroll.

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?

Two short sentences, no waste, with the capability stated first and the applicability constraint appended. The 'X11 only' fragment is terse but appropriate.

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 four undocumented parameters and no annotations, a single sentence plus a platform note is thin. An output schema exists, so return values needn't be described, but the unspecified semantics of 'clicks' and the no-coordinates fallback leave gaps an agent must guess at.

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 description coverage is 0% across four parameters, so the description must compensate and largely does not. It clarifies direction as up/down and that coordinates are optional, but the 'clicks' parameter (default 3) is never explained — whether it means scroll notches or repeated events is left entirely to inference.

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 and resource (scroll the mouse wheel) with its two axes (up/down) and optional targeting at coordinates. This clearly distinguishes it from click, double_click, drag_mouse, and move_mouse siblings, though it does not name them.

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 by the verb plus the 'X11 only' constraint, which tells the agent when the tool is even applicable. There is no explicit guidance on when to scroll vs. use drag or click, and no note about pointer/focus prerequisites.

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