Skip to main content
Glama
Electron Debug MCP Server

Electron Debug MCP Server

by amafjarkasi

set_window_bounds

Move or resize an Electron BrowserWindow by setting x, y, width, and height; omit any field to leave it unchanged. Requires inspectMain and does not reveal hidden windows.

Instructions

Move or resize a BrowserWindow. Omit a field to leave it unchanged. Requires inspectMain. Does not show a hidden window.

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

Input Schema

NameRequiredDescriptionDefault
xNo
yNo
widthNo
heightNo
windowIdNoBrowserWindow.id from webcontents_topology
processIdNoProcess ID. If omitted, uses the single running app.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.15.1

TDQS

A4/5.0
Behavior4/5

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

Annotations only supply destructiveHint=false, so the description carries most of the burden and does so: it discloses partial-update semantics, an authorization prerequisite (inspectMain), and a behavioral limit (hidden windows are not revealed). It doesn't say what happens on failure or whether the change is reversible.

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 action, then the calling convention, then the constraints. No filler or redundant restatement of the 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?

For a small, no-output-schema mutation tool this covers the essentials: what it changes, how to do partial updates, and what it requires. Only failure behavior and whether the window must already be attached are unaddressed.

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?

With 33% schema coverage and 6 optional parameters, the description adds the important cross-parameter rule that omitted fields stay unchanged, which the schema cannot express. The schema itself documents windowId and processId, and x/y/width/height are self-evident, so no further param detail is strictly needed.

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 concrete verb pair (move/resize) and a concrete resource (BrowserWindow), which is enough for an agent to distinguish it from focus_window or set_clipboard. It stops short of naming a sibling explicitly, so it lands at 4 rather than 5.

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?

'Omit a field to leave it unchanged' gives the key calling pattern for a partial-update tool, and 'Requires inspectMain' plus 'Does not show a hidden window' define a prerequisite and an exclusion. What's missing is any routing guidance toward alternatives when the window is hidden or not inspectable.

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