Skip to main content
Glama
@yawlabs/electron-mcp

@yawlabs/electron-mcp

Official
by YawLabs

electron_configure_fuses

Read-onlyIdempotent

Generate Electron Fuse configurations to disable dangerous runtime features like ELECTRON_RUN_AS_NODE and NODE_OPTIONS, hardening production apps with recommended, strict, or custom security levels.

Instructions

Generate @electron/fuses configuration to harden your Electron app. Fuses are compile-time toggles that disable dangerous Electron features (like ELECTRON_RUN_AS_NODE, NODE_OPTIONS) and cannot be re-enabled by end users. Essential for production apps.

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": {
      "level": "<level>"
    },
    "name": "electron_configure_fuses"
  }
}

Input Schema

NameRequiredDescriptionDefault
levelYes'recommended' for sensible defaults, 'strict' for maximum security, 'custom' to specify each fuse individually
customFusesNoIndividual fuse settings (only for 'custom' level)

Schema Changelog

Changes observed during successful MCP inspections.

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

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is covered. The description adds genuinely useful behavioral context: fuses are compile-time toggles and cannot be re-enabled by end users, which tells the agent the change is effectively permanent for shipped builds. It stops short of saying whether a file is written or a config snippet is returned.

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 short sentences, front-loaded with the action and resource, with the security rationale following. The closing 'Essential for production apps' leans slightly promotional but still earns its place as usage signal.

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?

No output schema exists, and the description does not state what is produced (a JSON snippet, a Forge config edit, or a patch applied to a binary). For a generation tool that returns configuration rather than mutating state, that output-shape detail is the main remaining gap; parameter and safety coverage are otherwise adequate.

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 every fuse flag and its default documented in the input schema, so the schema carries the parameter burden. The description adds no syntax or interaction detail beyond what the schema states, making the baseline 3 appropriate.

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 specific verb and resource: 'Generate @electron/fuses configuration'. The purpose is immediately distinguishable from sibling tools like electron_configure_csp or electron_audit_security. It does not explicitly name a sibling, which keeps it just short of a 5.

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?

'Essential for production apps' gives an implied context for when to reach for this tool, and the level enum descriptions in the schema clarify the recommended/strict/custom choice. There is no explicit when-not guidance or named alternative for related security-hardening tasks.

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