Skip to main content
Glama
Electron Debug MCP Server

Electron Debug MCP Server

by amafjarkasi

press_key

Simulates a key press or keyboard shortcut in an Electron app, with optional modifiers and selector focus, to test interactions during debugging.

Instructions

Press a key or shortcut (Enter, Escape, Tab, Arrow*, or a character) with optional modifiers

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": {
      "key": "<key>"
    },
    "name": "press_key"
  }
}

Input Schema

NameRequiredDescriptionDefault
keyYesKey name, e.g. "Enter", "Escape", "a", "Tab", "ArrowDown"
repeatNo
selectorNoOptional CSS selector to focus before keypress
targetIdNo
modifiersNoModifier keys, e.g. ["Control"] for Ctrl+A
processIdNoTarget process ID. Omit if only one app is running.

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 carries most of the burden. It does not say where the keystroke is delivered (focused element vs. selector/targetId/processId), whether it waits for the keypress, or what happens if no matching window exists. 'Optional modifiers' is the only behavioral hint added.

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; the core action and accepted values come first. It is appropriately sized for a simple keystroke tool, though the parenthetical could be tightened.

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?

With six parameters, three of them undocumented in the schema and no output schema, the description should clarify targeting behavior (selector/targetId/processId) and repeat semantics. It leaves the agent to infer how the key is routed and what the result looks like.

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 67%, so the baseline is roughly a 3, and the description largely echoes the schema's own key examples ('Enter', 'Escape', 'Tab', 'Arrow*'), adding only the implicit note that a single character is valid. It says nothing about repeat (capped at 50), selector, targetId, or processId, so it does not compensate for the uncovered parameters.

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 gives a specific verb ('Press') plus the resource ('a key or shortcut') and enumerates accepted key forms (Enter, Escape, Tab, Arrow*, or a character), which makes the action concrete and distinct from generic input tools. It stops short of naming any sibling (e.g. click, fill_form, evaluate) to differentiate itself, so it is clear but not comparative.

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 statement of when to use this tool versus alternatives such as click or fill_form, nor any prerequisite (e.g. an app must be running/focused). The only guidance is the parenthetical listing of key names, which describes inputs rather than selection criteria.

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