Skip to main content
Glama
Electron Debug MCP Server

Electron Debug MCP Server

by amafjarkasi

trigger_shortcut

Triggers an Electron global shortcut accelerator, such as Ctrl+Shift+P or F12, to test or reproduce keyboard-driven app behavior during debugging.

Instructions

Trigger an Electron global shortcut accelerator (e.g. 'CommandOrControl+Shift+P')

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "accelerator": "<accelerator>"
    },
    "name": "trigger_shortcut"
  }
}

Input Schema

NameRequiredDescriptionDefault
targetIdNo
processIdNoProcess ID. If omitted, uses the single running app.
acceleratorYesKeyboard shortcut accelerator (e.g. 'Ctrl+Shift+P', 'F12')

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.15.1

TDQS

C2.7/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 carries the burden of disclosure and adds little. It does not explain what happens if the accelerator is unregistered, whether the shortcut fires at the OS level versus into the app window, whether focus is required, or what errors surface when no app is running.

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?

It is a single front-loaded sentence with zero filler, and the example is placed inline where it is useful. Its brevity is efficient, though the terseness is also what leaves the gaps elsewhere.

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 tool with no output schema, three parameters, and only a single annotation, the description should explain at least precondition state (app attached/focused) and failure behavior. Neither is present, and the undocumented targetId parameter remains unexplained.

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 coverage is 67%, with targetId carrying no description at all. The description's parenthetical accelerator example simply duplicates the accelerator parameter's own schema example, adding no new meaning, and it says nothing about targetId or processId disambiguation.

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 names a specific verb and resource ('Trigger an Electron global shortcut accelerator') and includes a concrete accelerator example, so the agent knows exactly what operation is performed. It does not, however, distinguish itself from sibling input-injection tools such as click, click_ax, or evaluate.

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?

There is no when-to-use or when-not-to-use guidance. The description never says whether the target app must be attached or focused first, nor when to prefer this over other input tools like click or evaluate, leaving the agent to infer all usage context.

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