Skip to main content
Glama
@yawlabs/electron-mcp

@yawlabs/electron-mcp

Official
by YawLabs

electron_configure_auto_update

Read-onlyIdempotent

Generates electron-updater auto-update configuration, including main process setup, update handling, notification UI, and signing requirements for GitHub, S3, or generic HTTP update servers.

Instructions

Generate complete auto-update configuration using electron-updater. Produces main process setup, update event handling, renderer notification UI code, and platform-specific signing requirements. Supports GitHub releases, S3, and generic HTTP update servers.

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": {
      "provider": "<provider>"
    },
    "name": "electron_configure_auto_update"
  }
}

Input Schema

NameRequiredDescriptionDefault
providerYesUpdate distribution method: 'github' (GitHub Releases), 's3' (AWS S3), 'generic' (any HTTP server)
s3BucketNoS3 bucket name (for 's3' provider)
genericUrlNoBase URL for updates (for 'generic' provider)
githubRepoNoGitHub repo name (for 'github' provider)
githubOwnerNoGitHub owner (for 'github' provider)
autoDownloadNoAutomatically download updates (default true)
autoInstallOnQuitNoInstall update on app quit (default true)

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

B3.2/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 adds useful behavioral context about what the output contains (four distinct code artifacts and signing requirements), but it never clarifies the key ambiguity for a 'read-only' generator: whether code is only returned or also written into the project.

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 core action, followed by the produced artifacts and supported providers. Every sentence carries information; only the provider list mildly duplicates the schema enum.

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?

With no output schema present, the description appropriately compensates by enumerating the generated artifacts and the supported distribution backends. It is nearly complete for a code-generation tool, with the only meaningful gap being whether files are written to disk or content is merely returned.

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%, so all seven parameters, including the provider enum and the provider-specific fields, are already documented in the schema. The description reinforces this by naming the three supported providers, but adds no format, precedence, or conditional-requirement detail beyond what the schema supplies.

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 complete auto-update configuration using electron-updater') and enumerates the concrete artifacts produced (main process setup, event handling, renderer notification UI, signing requirements). No sibling tool addresses auto-update, so it is distinguishable in practice, though the description never explicitly names a sibling to contrast with.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use or when-not-to-use guidance, no stated prerequisites (e.g. an existing scaffolded project), and no mention of alternatives. The only implied guidance is that the tool applies when you need auto-update, which the agent must infer from the name and description.

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