Skip to main content
Glama
@yawlabs/electron-mcp

@yawlabs/electron-mcp

Official
by YawLabs

electron_explain_concept

Read-onlyIdempotent

Explains Electron concepts with version-aware accuracy to replace outdated tutorials, covering process model, context isolation, sandbox, IPC, ASAR, fuses, code signing, and build tool comparison.

Instructions

Get a clear, authoritative explanation of an Electron concept. Counters outdated tutorial content with accurate, version-aware information. Covers: process model, context isolation, sandbox, IPC, ASAR, fuses, code signing, and build tool comparison.

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": {
      "concept": "<concept>"
    },
    "name": "electron_explain_concept"
  }
}

Input Schema

NameRequiredDescriptionDefault
conceptYesThe Electron concept to explain

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.8/5.0
Behavior3/5

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

Annotations already declare this a safe, idempotent, closed-world read, so the safety profile is covered. The description adds a real behavioral claim, that answers are version-aware and intended to correct stale tutorials, but says nothing about the shape or depth of the explanation returned, and no output schema exists to fill that gap.

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 before the differentiator and the coverage list. The final topic list duplicates the enum values somewhat, but it is compact framing rather than padding.

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?

For a single-parameter, read-only explanation tool with full schema coverage and clear annotations, this is nearly complete. The only meaningful omission is any hint about the form or scope of the returned explanation, which matters somewhat given the absence of an output schema.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

There is a single required parameter whose schema already gives 100% coverage and an enum of all valid values. The description reinforces the meaning by spelling out the concept list (process model, context isolation, sandbox, IPC, ASAR, fuses, code signing, build tool comparison) in human-readable form, which is correctly scoped rather than merely repeated.

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?

A specific verb plus resource: 'Get a clear, authoritative explanation of an Electron concept', with the covered topics enumerated. It clearly differs from the audit and scaffold siblings, though it does not acknowledge the overlap with electron_explain_process_model even though 'process-model' is one of its accepted concepts.

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 phrase 'Counters outdated tutorial content with accurate, version-aware information' implies when this tool is preferred over general knowledge, which is useful implied guidance. It never states when not to use it, nor names an alternative such as electron_knowledge_version for version lookups, leaving routing to inference.

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