Skip to main content
Glama
@yawlabs/electron-mcp

@yawlabs/electron-mcp

Official
by YawLabs

electron_migrate_version

Read-onlyIdempotent

Generate a migration checklist for upgrading Electron versions, listing breaking changes, deprecated APIs, and required code modifications between your current and target versions.

Instructions

Generate a migration checklist for upgrading between Electron versions. Lists all breaking changes, deprecated APIs, and required code modifications between the current and target versions.

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": {
      "currentVersion": "<currentVersion>",
      "targetVersion": "<targetVersion>"
    },
    "name": "electron_migrate_version"
  }
}

Input Schema

NameRequiredDescriptionDefault
targetVersionYesTarget Electron major version (e.g. 41)
currentVersionYesCurrent Electron major version (e.g. 28)

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

A3.5/5.0
Behavior3/5

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

Annotations already declare the tool as read-only, idempotent, non-destructive, and closed-world. The description adds useful context about the checklist content, including breaking changes and deprecated APIs, but it does not describe the output format, whether source code is required, or other operational details. This is adequate but leaves meaningful behavioral gaps.

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 two tight sentences with the core action and scope front-loaded. Every sentence contributes directly to understanding what the tool produces. There is no repetitive or unnecessary wording.

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?

For a simple two-parameter read-only tool with no output schema, the description gives a reasonable summary of what the checklist contains. However, because there is no output schema, it should ideally specify the return format or shape more clearly. It is minimally adequate but not fully complete.

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 the two integer version parameters are already well documented. The description adds only modest semantic context by indicating that the comparison is between the current and target versions. It does not add format details, constraints, or examples beyond the schema.

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: generating a migration checklist for upgrading between Electron versions. It clearly says the tool lists breaking changes, deprecated APIs, and required code modifications. It does not explicitly differentiate itself from siblings such as electron_check_deprecated_apis or electron_knowledge_version.

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 implied by 'upgrading between Electron versions', so an agent can infer this is for migration planning. However, the description gives no explicit when-to-use guidance, prerequisites, or guidance to prefer this over sibling tools. There are no stated exclusions or alternatives.

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