Skip to main content
Glama

macos_mouse_scroll

Scroll at the current cursor position on macOS by specifying vertical and optional horizontal amounts in lines or pixels; Accessibility permission is required.

Instructions

macOS only. Scroll at the current cursor position. Vertical amount is required (positive up, negative down); horizontal is optional. Defaults to line units. Requires Accessibility permission.

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": {
      "amount": "<amount>"
    },
    "name": "macos_mouse_scroll"
  }
}

Input Schema

NameRequiredDescriptionDefault
unitNoScroll unit. Defaults to lines (safe everywhere); pixels needs high-resolution scroll support.
amountYesVertical scroll amount. Positive scrolls up, negative scrolls down (before OS natural-scroll).
horizontalNoHorizontal amount. Positive scrolls right, negative left. Defaults to 0.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does reasonably well: it discloses that scrolling targets whatever is under the current cursor position (so the agent must move first), that a line-unit default applies, and that Accessibility permission is required. It omits what happens when permission is missing (error vs. silent no-op) and whether the call is synchronous, which are the remaining behavioral gaps.

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

Conciseness5/5

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

Four short sentences, front-loaded with the platform constraint, then the action, then parameter direction, then the permission prerequisite. Nothing is wasted and the ordering matches how an agent evaluates feasibility before calling.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a three-parameter, single-required-argument tool with full schema coverage and no output schema, the description covers platform, targeting model, units, and permissions. The only material omission is failure behavior when Accessibility permission is absent, which matters for an OS-level input tool.

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 100%, so the schema already documents unit, amount direction, and horizontal defaults. The description restates the sign convention and unit default rather than adding new meaning such as scroll magnitude guidance or natural-scroll interaction. Baseline 3 is appropriate when the schema does the heavy lifting.

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 definition opens with a concrete verb and resource: "Scroll at the current cursor position," plus a platform qualifier (macOS only). That is far more specific than a tautology and tells an agent this is a system-level input event rather than a page-scoped scroll. It stops short of naming a sibling such as tab_scroll, so an agent must infer from "macOS only" and "cursor position" that browser-tab scrolling belongs elsewhere.

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?

"macOS only" functions as a when-not condition and implicitly excludes the tab_* family, which is useful routing information. However, there is no explicit statement of when to prefer this over tab_scroll or macos_mouse_drag, nor any precondition guidance beyond the permission note.

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