Skip to main content
Glama

Scroll

scroll

Dispatches discrete mouse wheel deltas to control vertical and horizontal movement; positive dy moves down, negative dy moves up.

Instructions

Dispatches discrete mouse wheel scroll deltas (positive dy=down, negative dy=up).

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": {
      "dx": "<dx>",
      "dy": "<dy>"
    },
    "name": "scroll"
  }
}

Input Schema

NameRequiredDescriptionDefault
dxYes
dyYes
pidNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare non-read-only, non-destructive, non-idempotent, closed-world behavior, so the safety profile is covered. The description adds genuinely useful behavior in the sign convention (positive dy=down, negative dy=up), but says nothing about delta units (pixels vs. lines), whether scrolling is animated, or what happens when no pid is given.

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 tightly written sentence with the key semantic detail front-loaded; nothing is wasted. Its brevity is efficient rather than padded, though it is arguably too terse to be fully useful.

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?

For a 3-parameter input tool with zero schema descriptions and no output schema, one sentence covering only dy is not enough. An agent cannot determine how to use dx, how to target a specific window via pid, or what magnitude of delta is meaningful.

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%, so the description must carry parameter meaning, and it only explains dy's sign convention. dx (horizontal scrolling) and pid (target process/window) are entirely undocumented in both schema and description, leaving two of three parameters semantically opaque.

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 ('Dispatches') and resource ('mouse wheel scroll deltas'), so the agent knows exactly what action is performed. It is clearly distinct from click/drag/type_text siblings by nature of the resource, though it never explicitly contrasts itself with 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 only implied: an agent can infer this is the tool for scrolling a view, but there is no statement of when to prefer scroll over drag or key_combination, nor any prerequisite such as needing a focused or targeted window. No exclusions or alternatives are named.

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