Skip to main content
Glama
Electron Debug MCP Server

Electron Debug MCP Server

by amafjarkasi

stop_app

Destructive

Terminates an Electron process launched by start_app or detaches bookkeeping from an attached debugging session, with an optional processId to target a specific app.

Instructions

Stop a process started by start_app, or detach bookkeeping for an attached session

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": "stop_app"
  }
}

Input Schema

NameRequiredDescriptionDefault
processIdNoProcess id returned by start_app or attach. If omitted, uses the single running app.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.15.1

TDQS

A3.6/5.0
Behavior3/5

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

Annotations supply only destructiveHint=true, so the description carries the disclosure burden. It usefully distinguishes two outcomes — terminating a started process versus only removing bookkeeping for an attached session — but never says whether the stop is graceful, whether the target process survives either path, or what an error looks like.

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?

One sentence, no filler, and the primary meaning (stop a start_app process) is front-loaded ahead of the secondary detach case.

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 one-optional-parameter destructive tool with no output schema, the description covers purpose, both operating modes, and the originating tools. Remaining gaps are behavioral detail (graceful vs hard stop, multi-app ambiguity) rather than structural omissions.

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% with a single optional processId, and the schema description already explains the 'single running app' fallback. The description adds no format or semantics beyond that, so baseline 3 applies.

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?

States a specific verb ('Stop') plus the resource ('a process started by start_app') and a second, distinct mode ('detach bookkeeping for an attached session'). That dual framing separates it from the profiling/screencast siblings (stop_coverage, stop_cpu_profile, stop_tracing) whose names imply different resources.

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 through provenance: call this when the process came from start_app or attach. There is no explicit when-not guidance (e.g., what to do if multiple apps are running, or when to prefer detaching over killing), so the agent must infer the boundary.

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

Deploy Server

Other Tools