Skip to main content
Glama
@yawlabs/electron-mcp

@yawlabs/electron-mcp

Official
by YawLabs

electron_diagnose_build_error

Read-onlyIdempotent

Diagnose Electron build and packaging errors from electron-builder, forge, or packager output, identifying code signing, native module, ASAR, platform config, and path resolution issues.

Instructions

Diagnose Electron build/packaging errors from electron-builder, electron-forge, or electron-packager output. Identifies common failures: code signing errors, native module rebuild issues, ASAR packaging problems, missing platform-specific configuration, and __dirname path resolution bugs.

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": {
      "errorOutput": "<errorOutput>"
    },
    "name": "electron_diagnose_build_error"
  }
}

Input Schema

NameRequiredDescriptionDefault
platformNoTarget platform. Defaults to 'unknown' (auto-detect).
buildToolNoWhich build tool produced the error. Defaults to 'unknown' (auto-detect).
errorOutputYesThe build error output (stderr/stdout) to diagnose

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.7.2
    • removedInput schema / additionalProperties
      Removed value: -false
  2. First observedv1.2.13

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds genuine value by naming the specific failure categories the analysis can surface, though it does not state that it only analyzes the supplied text (no build is re-run) or what happens with unparseable output.

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?

Two tight sentences, front-loaded with the action and resource, followed by the enumerated coverage. No filler or restatement of the title.

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 read-only single-input diagnostic tool this is nearly complete; the coverage list effectively hints at the returned findings. With no output schema, a brief note on the shape of the diagnosis result (e.g., matched category plus suggested fix) would close the only real gap.

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 enums and defaults ('auto-detect') already documented in the schema. The description adds no per-parameter detail such as what 'errorOutput' should contain or whether full logs help, so the baseline 3 applies.

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?

A specific verb ('Diagnose') plus a specific resource ('Electron build/packaging errors') scoped to output from electron-builder, electron-forge, or electron-packager. It further enumerates the failure classes it recognizes (code signing, native module rebuild, ASAR packaging, platform config, __dirname bugs), which makes it obviously distinct from the audit/configure/scaffold siblings.

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?

The trigger condition is clear: call this when you have build or packaging error output from one of the three named tools. No explicit when-not guidance or alternatives are given, but within this sibling set the usage context leaves little ambiguity.

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