Skip to main content
Glama

desktop_mouse_wheel

Scroll vertically or horizontally at absolute screen coordinates and apply modifier keys for precise desktop UI navigation.

Instructions

agent-desktop mouse-wheel: Scroll the mouse wheel at absolute coordinates (requires --headed)

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": {
      "x": "<x>",
      "y": "<y>"
    },
    "name": "desktop_mouse_wheel"
  }
}

Input Schema

NameRequiredDescriptionDefault
xYesAbsolute X coordinate for wheel event; write a negative value with = (--x=-100)
yYesAbsolute Y coordinate for wheel event; write a negative value with = (--y=-100)
dxNoHorizontal wheel lines; positive scrolls right, negative scrolls left
dyNoVertical wheel lines; positive scrolls up, negative scrolls down (default -3 when --dx is absent, else 0)
modifiersNoHeld modifiers: shift, meta, ctrl, alt (repeatable; cmd is accepted)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations supplied, the description carries the full behavioral burden, and it does disclose one genuinely useful constraint: the tool only works in headed mode. It says nothing about whether the scroll is synchronous, how the wheel event interacts with focus/hover state, or what is returned, leaving meaningful gaps for a UI-mutating tool.

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 tight sentence with the key constraint front-loaded and no filler. The 'agent-desktop mouse-wheel:' prefix duplicates the tool name and is the only wasted token.

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

Completeness3/5

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

For a five-parameter tool with a fully documented schema and no output schema, the description covers the essentials plus the headed-mode requirement. It is still thin on runtime behavior (return value, whether the scroll is applied immediately or queued), which matters because no annotations are available to fill that gap.

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%, including direction semantics for dx/dy and the conditional default for dy, so the schema already does the semantic work. The description adds no parameter meaning beyond restating that coordinates are absolute, which is the baseline-3 case.

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 names a specific verb and resource ('Scroll the mouse wheel') plus the target ('at absolute coordinates'), which clearly separates it from siblings like desktop_mouse_click or desktop_mouse_move. It stops short of explicitly naming when a sibling such as desktop_drag would be preferred, so it is clear but not fully differentiated.

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?

The only guidance is the parenthetical '(requires --headed)', which is a prerequisite rather than a when-to-use rule. There is no statement of when to choose wheel scrolling over desktop_mouse_click/drag or of any conditions under which this tool should be avoided.

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