Skip to main content
Glama
Electron Debug MCP Server

Electron Debug MCP Server

by amafjarkasi

drag

Simulates pointer press, move, and release between two selectors and dispatches text/plain HTML5 dataTransfer data so drop listeners receive the payload.

Instructions

Press on fromSelector, move to toSelector, and release. Also sends an HTML5 drag with text/plain dataTransfer so drop listeners receive the payload. Pass data to override the source text.

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": {
      "fromSelector": "<fromSelector>",
      "toSelector": "<toSelector>"
    },
    "name": "drag"
  }
}

Input Schema

NameRequiredDescriptionDefault
dataNotext/plain payload. Defaults to the source element's text.
targetIdNo
processIdNoTarget process ID. Omit if only one app is running.
toSelectorYes
fromSelectorYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.15.1

TDQS

A3.6/5.0
Behavior3/5

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

Annotations carry only destructiveHint=false, so the description does most of the work and usefully discloses the dual mechanism: synthetic mouse events plus an HTML5 dragstart/drop payload. It does not say what happens when the target has no drop listener, whether the drag is cancelable, or whether the source element must be interactable, leaving real behavioral gaps for an interaction tool.

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 tight sentences, front-loaded with the core press-move-release mechanic followed by the HTML5 detail and the override rule. No filler and nothing repeated from structured fields.

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 five-parameter interaction tool with no output schema, the description covers the essential mechanics and the primary payload behavior. The remaining gap is targetId, which is undescribed everywhere, though it is likely a standard scoping parameter across sibling tools.

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 40%. The description explains fromSelector, toSelector and clarifies that data overrides the source text (slightly beyond the schema's own wording), but targetId is undocumented in both the schema and the description, and processId is left entirely to the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a precise verb and resource (drag) and spells out the mechanics: press on fromSelector, move to toSelector, release. It also discloses that an HTML5 drag with text/plain dataTransfer is synthesized, which is exactly what separates this from a plain click or click_ax call.

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?

There is no when-to-use or when-not-to-use guidance beyond the implicit fact that it moves between two elements. It never names an alternative approach (e.g. click-then-click, or a manual press/move/release sequence) or states prerequisites such as both elements being visible or the page being focused.

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