Skip to main content
Glama
Electron Debug MCP Server

Electron Debug MCP Server

by amafjarkasi

click_menu_item

Clicks a native application menu item by path, ID, or role to automate Electron menu actions during debugging.

Instructions

Trigger a click on a native application menu item by path (e.g. 'File > Open File...'), id, or role

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

Input Schema

NameRequiredDescriptionDefault
idNoMenuItem ID if assigned
pathNoFull menu item path e.g. 'File > Save' or 'View > Toggle Developer Tools'
roleNoStandard role e.g. 'undo', 'cut', 'copy'
targetIdNo
processIdNoProcess ID. If omitted, uses the single running app.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.15.1

TDQS

C2.9/5.0
Behavior2/5

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

The only annotation is destructiveHint=false, so the description must carry most behavioral disclosure. It does not say whether the target app must be focused or attached, whether menus must already be open, what happens if the item is disabled, how ambiguity between multiple matches is resolved, or what a successful invocation returns. It adds some context by naming three lookup strategies, but that is largely parameter semantics rather than behavior.

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?

It is a single front-loaded sentence with no filler. The example path is useful and the sentence ends cleanly without redundant wording.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a UI-automation mutation tool with five parameters, no output schema, and only a single annotation, the description is quite thin. It omits prerequisites such as the app needing to be running or attached, failure behavior for missing or disabled menu items, and any hint about post-click effects such as dialogs opening.

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 80%, so the schema already documents id, path, role, and processId. The description restates the same three lookup modes and gives a path example, but adds little beyond the schema's own descriptions and does not mention targetId or processId.

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?

The description states a specific verb and resource: triggering a click on a native application menu item, with three targeting mechanisms. The phrase 'native application menu item' helps distinguish it from generic click tools like click or click_ax, though it does not explicitly name those siblings.

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

Usage Guidelines2/5

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

The description implies when the tool is useful (clicking menu items) but gives no explicit when-to-use guidance, no alternatives, and no prerequisite such as attaching to an application first. It also does not explain when to prefer path vs. id vs. role, or suggest using get_application_menu to discover menu items.

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