Skip to main content
Glama
@yawlabs/electron-mcp

@yawlabs/electron-mcp

Official
by YawLabs

electron_scaffold_project

Read-onlyIdempotent

Generate a complete Electron project scaffold with secure process separation, TypeScript, framework and build setup, security defaults, and an example IPC channel ready for development.

Instructions

Generate a complete, secure, modern Electron project scaffold. Includes proper process separation, TypeScript configuration, framework integration, build tooling, security defaults, and an example IPC channel. Produces a full project structure ready to develop.

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

Input Schema

NameRequiredDescriptionDefault
nameYesProject name (lowercase, hyphens ok), e.g. 'my-electron-app'
featuresNoOptional features to include
buildToolNoBuild tool. Defaults to 'electron-vite'.
frameworkNoFrontend framework. Defaults to 'react'.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.7.2
    • removedInput schema / additionalProperties
      Removed value: -false
  2. Changed1 schema field changedv1.2.15
    • addedInput schema / properties / name / pattern
      Added value: +"^[a-z0-9][a-z0-9._-]*$"
  3. First observedv1.2.13

TDQS

B3/5.0
Behavior1/5

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

Annotations declare readOnlyHint=true, yet the description says the tool will 'Generate' and 'Produce a full project structure', i.e. create files on disk, which is a side effect rather than a read. The description also omits critical behavior for a generator: where files are written, whether an existing directory is overwritten, and whether it returns contents or a path.

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 front-loaded sentences with an efficient capability list. The closing clause 'ready to develop' is mildly redundant with 'complete... scaffold' but the text is otherwise tight and well ordered.

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?

With no output schema, the description should state what the agent gets back (generated file tree, target path, or inline contents) and whether it writes to disk or previews. Those omissions matter for a generator with four parameters, though the feature list gives a reasonable sense of scope.

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% and the enums for buildTool, framework, and features are self-explanatory, so the schema carries the parameter burden. The description adds nothing beyond the schema — it does not explain defaults (electron-vite, react) or how the selected framework/buildTool shape the generated output.

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?

Uses a specific verb+resource pair ('Generate a complete... Electron project scaffold') and enumerates what the output contains (process separation, TypeScript config, framework integration, build tooling, security defaults, example IPC channel). It is clearly distinguishable from audit/lint/configure siblings, but it never names a sibling such as electron_generate_preload_bridge or electron_scaffold_ipc_channel to draw the boundary.

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 only implied: 'Produces a full project structure ready to develop' signals a project-start/bootstrapping scenario, but there is no explicit when-to-use, when-not-to-use, or alternative (e.g., use the ipc_channel tool to add channels to an existing project).

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