Skip to main content
Glama
Electron Debug MCP Server

Electron Debug MCP Server

by amafjarkasi

get_application_menu

Read-only

Inspect the native Electron application menu hierarchy, including items, roles, accelerators, and enabled states, to debug menu structure and state for a running or targeted app process.

Instructions

Inspect the native Electron application menu hierarchy, items, roles, accelerators, and enabled states

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

Input Schema

NameRequiredDescriptionDefault
targetIdNo
processIdNoProcess ID. If omitted, uses the single running app.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.15.1

TDQS

B3.2/5.0
Behavior3/5

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

readOnlyHint=true already tells the agent this is a safe read, so the description's real contribution is the disclosure of returned content (hierarchy, roles, accelerators, enabled states), which is useful since no output schema exists. It does not say what happens when no app is running, how multiple apps are disambiguated, or whether the hierarchy is fetched live from the renderer.

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?

A single front-loaded sentence with no filler. It is efficient, though the enumeration of menu facets is packed into one clause without structure, and no usage framing is front-loaded ahead of it.

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?

For a two-parameter read tool with readOnly annotations and no output schema, the description covers what is inspected but leaves gaps: the meaning of targetId, behavior with multiple running apps, and any guidance tying it to click_menu_item. Adequate but not complete.

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

Parameters2/5

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

Schema description coverage is only 50%: processId is documented with its fallback, but targetId is bare in the schema and completely unaddressed in the description. The description contributes nothing to parameter meaning, so the undocumented parameter remains unexplained.

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 (Inspect) and a specific resource (native Electron application menu hierarchy), then enumerates what is surfaced: items, roles, accelerators, enabled states. An agent can tell this is a read-model tool rather than the sibling click_menu_item, though it never explicitly contrasts the two.

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 use case is implied by 'Inspect' – read the menu model before acting on it – but there is no explicit when-to-use, no mention of click_menu_item as the mutation alternative, and no stated prerequisites such as an attached app or an already-discovered target.

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