Skip to main content
Glama
@yawlabs/electron-mcp

@yawlabs/electron-mcp

Official
by YawLabs

electron_generate_window_manager

Read-onlyIdempotent

Generates multi-window management boilerplate for Electron apps, creating a WindowManager class for lifecycle, IPC, state persistence, and cleanup.

Instructions

Generate multi-window management boilerplate for Electron apps. Creates a WindowManager class that handles window lifecycle, inter-window communication, window state persistence, and proper cleanup. Supports common patterns like main + child windows, modal dialogs, and detached panels.

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": {
      "windows": "<windows>"
    },
    "name": "electron_generate_window_manager"
  }
}

Input Schema

NameRequiredDescriptionDefault
windowsYesWindows to manage
persistStateNoWhether to persist window positions/sizes across restarts (default true)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.7.2
    • removedInput schema / additionalProperties
      Removed value: -false
    • removedInput schema / properties / windows / items / additionalProperties
      Removed value: -false
  2. First observedv1.2.13

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description usefully adds the content of the generated artifact, but it never resolves the key behavioral question for a generator with readOnlyHint=true: whether code is written to disk or returned as a payload. That omission, plus no mention of overwrite behavior on re-generation, is a real gap even at the lower annotated bar.

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?

Three sentences, front-loaded with the action and then the capability list, with no filler or repetition. Slightly more could be trimmed, but every sentence carries distinct information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description should say what the caller receives (file paths, a code string, a directory of files) and where it lands. It describes the generated class's capabilities instead, so an agent knows the purpose but not the return shape or side effects — a meaningful omission for a code-generation tool.

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 100% with only two parameters, so the schema already documents the window id/url/type/title/width/height fields and persistState. The phrase 'window state persistence' loosely maps to persistState, but the description adds no format, default, or constraint detail beyond the schema, so the baseline 3 applies.

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 ('Generate multi-window management boilerplate for Electron apps') and then enumerates what the generated artifact does: lifecycle, inter-window communication, state persistence, cleanup. It stops short of naming any sibling tool or explaining how it differs from electron_scaffold_project or electron_generate_preload_bridge, so an agent must infer the boundary.

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 through the pattern list ('main + child windows, modal dialogs, detached panels'), which hints at the scenarios this fits. There is no explicit when-to-use statement, no when-not-to-use, and no prerequisites such as a required project scaffold or Electron version that would route an agent between this and the scaffolding siblings.

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