Skip to main content
Glama
Electron Debug MCP Server

Electron Debug MCP Server

by amafjarkasi

focus_window

Brings an Electron BrowserWindow to the foreground by showing and focusing it, optionally moving it to the top. Omit windowId to target the first window.

Instructions

Bring an Electron BrowserWindow forward (show, focus, moveTop). Requires inspectMain. Omit windowId to use the first window. Pass show:false to focus without showing 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": "focus_window"
  }
}

Input Schema

NameRequiredDescriptionDefault
showNoCall show() before focus. Default true.
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

A3.9/5.0
Behavior4/5

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

Beyond the minimal destructiveHint=false annotation, the description discloses the underlying operations (show, focus, moveTop), the prerequisite (inspectMain), the default window-selection behavior, and the hidden-window focus behavior. That is strong behavioral context for a simple window-focusing 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?

The description is compact and front-loaded, with each sentence adding a distinct operational detail. There is no redundant or filler wording.

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 simple three-parameter, no-output-schema tool, the description covers the main action, prerequisites, defaults, and one important edge behavior. A little more guidance about failure modes or process selection could make it fully complete, but the essentials are present.

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 100%, so the baseline is 3, but the description adds meaningful semantics for windowId omission and show:false behavior that go beyond the schema text. It does not add much for processId, but the schema already explains that parameter.

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 states a specific verb and resource: bringing an Electron BrowserWindow forward via show, focus, and moveTop. It is clear what the tool does, though it does not explicitly contrast itself with nearby window-related siblings such as set_window_bounds.

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?

It gives useful invocation context: requires inspectMain, omitting windowId targets the first window, and show:false focuses without revealing a hidden window. It does not explicitly state when to prefer this over alternatives or when not to use it.

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