Skip to main content
Glama
Electron Debug MCP Server

Electron Debug MCP Server

by amafjarkasi

find_installed_apps

Read-onlyIdempotent

Scans common installation directories to locate packaged Electron apps (.app, .exe, .desktop) for debugging and process management.

Instructions

Scan common install locations for packaged Electron apps (.app / exe / .desktop)

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

Input Schema

NameRequiredDescriptionDefault

No arguments

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?

The annotations already declare readOnlyHint and idempotentHint, so safety and repeatability are covered without the description. The description still adds useful behavior: it is a filesystem scan, it is scoped to common install locations (so results are not exhaustive), and it matches only packaged bundles rather than source checkouts. It omits whether the scan is slow, whether it descends into subdirectories, and what it returns.

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?

A single sentence with the verb and scope front-loaded and no filler. The parenthetical format list is dense, load-bearing information rather than padding.

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 parameters and no output schema, the description carries the full burden of explaining what comes back, and it does not say whether the result is a list of paths, app names, bundle identifiers, or per-platform records. For a zero-arg discovery tool that is the main remaining gap; the scanning scope itself is adequately covered.

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

Parameters4/5

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

The tool takes zero parameters, so there is no parameter meaning to add and the baseline of 4 applies. Nothing in the description mischaracterizes the signature.

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 concrete verb ("Scan") and a concrete resource (common install locations for packaged Electron apps), plus the artifact types it looks for (.app / exe / .desktop). This is far more specific than a bare name restatement, but it never distinguishes itself from the discovery siblings (find_apps, discover_apps, list_apps), which an agent would 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?

Usage is implied rather than stated: the agent can infer this is the tool for locating Electron apps already installed on disk, as opposed to one running or launched. There is no explicit when-to-use, no when-not, and no named alternative among the several sibling discovery tools.

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