Skip to main content
Glama
Electron Debug MCP Server

Electron Debug MCP Server

by amafjarkasi

discover_apps

Read-onlyIdempotent

Scans a local port range for reachable Chrome DevTools Protocol endpoints to find an Electron app started with an unknown debug port.

Instructions

Scan a local port range (default: 9222-9235) for reachable Chrome DevTools Protocol endpoints. Useful when an app was started with an unknown debug port.

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

Input Schema

NameRequiredDescriptionDefault
endPortNo
startPortNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.15.1

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint and idempotentHint, so the safety profile is covered. The description adds that the scan is local and bounded to a port range with a stated default, but says nothing about scan duration, timeouts, or whether unreachable ports are silently skipped — behavior an agent might care about.

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?

Two front-loaded sentences with no filler: capability first, motivating scenario second. Nothing redundant or padded.

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 simple two-optional-parameter discovery tool with no output schema, the description covers what it does, its default scope, and when it matters. The main omission is what a successful result looks like (endpoint list vs. ports only), which is a modest gap rather than a blocking one.

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 0% and the schema is bare (integer, exclusiveMinimum 0), so the description carries the burden. It supplies the default range 9222-9235, which meaningfully informs the parameters, but never explains how startPort/endPort relate (inclusive/exclusive), what happens if start > end, or how far a scan may be widened.

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 and resource ('Scan a local port range ... for reachable Chrome DevTools Protocol endpoints') with the default range named inline. It does not explicitly distinguish itself from siblings like find_apps or attach, so an agent must infer that this one probes ports rather than enumerating known apps.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

'Useful when an app was started with an unknown debug port' gives a clear triggering scenario for the tool. It stops short of naming alternatives (e.g., use find_apps/attach when the port is known) or stating when not to use it, so it lands at clear-context-but-no-exclusions.

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