Skip to main content
Glama
@yawlabs/electron-mcp

@yawlabs/electron-mcp

Official
by YawLabs

electron_audit_performance

Read-onlyIdempotent

Analyze Electron app code for seven performance anti-patterns and get fixes for eager loading, synchronous main calls, extra startup windows, heavy preload scripts, and unbundled dependencies.

Instructions

Analyze Electron app code for 7 official performance anti-patterns: eager module loading, synchronous main-process operations, excessive BrowserWindows at startup, unnecessary polyfills, CDN-loaded assets, heavy preload scripts, and unbundled dependencies. Returns specific fixes.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "electron_audit_performance"
  }
}

Input Schema

NameRequiredDescriptionDefault
mainCodeNoMain process code to analyze
packageJsonNopackage.json content to check for bundling and dependencies
preloadCodeNoPreload script code to analyze
rendererCodeNoRenderer process code to analyze

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.7/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 the detection scope and states it returns specific fixes, which is useful, but it says nothing about behavior when inputs are omitted — a real concern given all four parameters are optional — nor about whether analysis is purely static.

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?

Two sentences, front-loaded with the verb and scope, and the second sentence carries genuinely distinct information (findings include fixes). The seven-item enumeration is slightly long but each item is a real detection capability rather than filler.

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?

There is no output schema, so mentioning that it returns specific fixes usefully compensates. For a read-only static audit with fully described parameters this is nearly complete; the remaining gap is guidance on supplying a subset of files versus all four.

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 four inputs (mainCode, packageJson, preloadCode, rendererCode) are already fully documented with their purpose and size limits. The description's category list loosely maps to those inputs but adds no format or minimum-input guidance beyond the schema.

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?

Specific verb plus resource ('Analyze Electron app code') scoped to performance, and the description enumerates all seven anti-pattern categories it detects, which distinguishes it from the security-focused siblings like electron_audit_security and electron_audit_ipc_security. An agent can tell what it checks without opening the schema.

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?

The category list implies the tool's use case (verifying performance characteristics of Electron code), but there is no explicit when-to-use statement, no when-not, and no named alternative such as the security audit tools for a non-performance review. Usage is inferable rather than stated.

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