Skip to main content
Glama
@yawlabs/electron-mcp

@yawlabs/electron-mcp

Official
by YawLabs

electron_explain_process_model

Read-onlyIdempotent

Explains Electron's multi-process architecture with version-aware guidance on main, renderer, preload, utility processes, contextBridge, and IPC patterns.

Instructions

Get a clear, version-aware explanation of Electron's multi-process architecture. Covers the main process, renderer processes, preload scripts, utility processes, contextBridge, and how they interact. Useful for understanding the mental model before building features.

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": {
      "topic": "<topic>"
    },
    "name": "electron_explain_process_model"
  }
}

Input Schema

NameRequiredDescriptionDefault
topicYesWhich aspect of the process model to explain
electronVersionNoTarget Electron version for version-specific guidance (e.g. '28', '33', '41'). Defaults to latest.

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
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive, and closed-world, so safety is covered. The description adds genuine context beyond them: the output is 'version-aware', meaning results shift with the target Electron version, and it scopes exactly which subsystems are explained.

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 compact sentences with the core purpose front-loaded, followed by scope and then usage framing. No filler, though the middle topic list partly duplicates the enum already visible in the schema.

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?

This is a simple two-parameter read-only explanation tool with rich annotations and no output schema, so the description does not need to describe return values. It covers what is explained and that guidance is version-specific, which is sufficient for correct invocation.

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 coverage is 100% and the topic enum is fully self-documenting, so the schema carries the parameter burden. The description's enumeration of covered subjects loosely maps onto the enum values but adds no format or selection guidance beyond what the schema already states.

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 names a specific verb and resource: 'Get a clear, version-aware explanation of Electron's multi-process architecture', and enumerates the concepts covered (main process, renderer, preload, utility, contextBridge, IPC). It does not, however, differentiate itself from the sibling electron_explain_concept, which an agent could reasonably confuse it with.

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?

'Useful for understanding the mental model before building features' implies a usage context (pre-implementation orientation) but gives no explicit when-not guidance and never names the nearest alternative, electron_explain_concept. The agent must infer the boundary from the description alone.

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