Skip to main content
Glama
Electron Debug MCP Server

Electron Debug MCP Server

by amafjarkasi

select_option

Selects an option in a element by value or visible label, then fires input and change events. Use it to set dropdown choices during Electron app debugging and UI testing.

Instructions

Choose an option in a by value or visible label, then fire input and change.

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": {
      "selector": "<selector>"
    },
    "name": "select_option"
  }
}

Input Schema

NameRequiredDescriptionDefault
labelNoVisible option label
valueNoOption value attribute
selectorYes
targetIdNo
processIdNoTarget process ID. Omit if only one app is running.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.15.1

TDQS

A3.5/5.0
Behavior3/5

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

Only destructiveHint=false is annotated, so the description carries most of the burden. It does add real behavioral value by disclosing that both input and change events are dispatched, which matters for framework-bound listeners. It omits failure behavior (option not found, non-select element), timing/auto-wait, and whether the value is matched exactly or by prefix.

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 compact sentence, front-loaded with the action and the selection strategies, with the side effect placed last. No filler or redundancy.

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 5-parameter DOM-mutation tool with no output schema and only a destructiveHint annotation, the description is thin. Required preconditions, resolution of selector versus targetId, and behavior when the option is absent are all left unstated.

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 60%, with selector and targetId documented nowhere. The description does resolve one genuine schema ambiguity by framing value and label as alternative selection strategies. But it does not say what happens if both value and label are supplied, nor does it explain selector or targetId semantics.

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+resource: 'Choose an option in a <select> by value or visible label' and states the side effect of firing input and change. It is clearly distinguishable from generic click/fill_session siblings conceptually, though it never names the closest alternative such as fill_form.

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 phrase 'in a <select>' implies the applicable context (native select elements only), which is useful scoping. However, it gives no explicit when-to-use versus fill_form/evaluate, no exclusions, and no prerequisites such as whether the element must be visible or scrolled into view.

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