Skip to main content
Glama
Electron Debug MCP Server

Electron Debug MCP Server

by amafjarkasi

scroll

Brings an element into view or moves the page or element using mouse wheel deltas in an Electron app.

Instructions

Scroll the page or an element. With a selector and no deltas, scrolls that element into view. With deltaY/deltaX, sends a mouse wheel at the element (or the viewport).

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

Input Schema

NameRequiredDescriptionDefault
deltaXNoHorizontal wheel delta. Positive scrolls right.
deltaYNoVertical wheel delta. Positive scrolls down. Default 400 when no selector.
selectorNoElement to scroll into view, or the wheel target
targetIdNo
processIdNoTarget process ID. Omit if only one app is running.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.15.1

TDQS

A4.1/5.0
Behavior4/5

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

Annotations supply only destructiveHint=false, so the description carries most of the burden, and it does explain the two underlying mechanisms (scroll-into-view vs synthetic wheel dispatch) rather than just saying 'scrolls'. It does not disclose whether the call waits for the scroll to settle or what is returned, but the core behavioral distinction is present.

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?

Three short sentences, front-loaded with the core action and then branching into the two parameter regimes. No filler and no restatement of the tool name.

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?

With five all-optional parameters, no output schema, and sparse annotations, the definition covers the decision-relevant combinations well enough to invoke correctly. The one remaining hole is targetId, which neither the schema nor the description explains.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 80%, so the baseline is 3; the description goes beyond it by explaining how parameters interact — selector alone targets scroll-into-view, selector plus deltas makes the element the wheel target, and deltas without a selector hit the viewport. The only unexplained parameter is targetId, which the schema also leaves undocumented.

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 opens with a specific verb and resource ('Scroll the page or an element') and then splits into two concrete modes, so an agent knows exactly what capability this provides. It stops short of distinguishing the tool from any sibling, but the two-mode framing already makes the operation unambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives operative conditional guidance: selector + no deltas means scroll-into-view, deltas mean dispatch a wheel event at the element or viewport. That is clear when-to-use context for the parameter combinations, but it does not state exclusions or name an alternative tool for related needs.

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