Skip to main content
Glama
Electron Debug MCP Server

Electron Debug MCP Server

by amafjarkasi

fill_form

Fill multiple text, password, checkbox, radio, dropdown, and file fields—plus optional submit—using labels, selectors, or accessibility refs, with {{secret:VAR}} resolution.

Instructions

Fill multiple input fields (text, password, checkboxes, radio buttons, dropdowns) and optionally submit in a single turn. Supports {{secret:VAR}} resolution and accessibility refs.

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": {
      "fields": "<fields>"
    },
    "name": "fill_form"
  }
}

Input Schema

NameRequiredDescriptionDefault
expectNoOptional UI assertion to verify post-submit outcome
fieldsYesForm field specifications or mapping of field names to values
submitNoSubmit selector/name/ref, or true to auto-detect submit button
targetIdNo
waitIdleNoWhether to wait for network idle after filling/submitting (default true)
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?

Annotations give openWorldHint=true and destructiveHint=false, so the risk profile is partly covered before reading the description. The description adds genuinely useful behavior beyond that - {{secret:VAR}} resolution and accessibility ref support - but says nothing about failure modes, whether partially filled forms are left dirty, how waitIdle defaulting to true affects timing, or what the expect assertion does when it fails.

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?

Two sentences, front-loaded with what gets filled and ending with the two non-obvious capabilities. Every clause carries information; nothing is repeated from the schema or annotations.

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 six-parameter tool with nested objects, an assertion sub-object, and no output schema, the definition covers the happy path but not the outcome. An agent cannot tell what the tool returns, whether a failed expect aborts the fill, or how targetId/processId scoping works - details it would need to call this reliably.

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 high (83%), so the baseline is 3. The description earns some credit by explaining that field targets may be accessibility refs and that values support secret placeholders, which clarifies the `fields`/`value` shape. It offers nothing on the undocumented remainder: expect, targetId, processId, and the submit selector 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?

States a specific verb+resource ("Fill multiple input fields") and enumerates the widget types covered (text, password, checkboxes, radio buttons, dropdowns) plus the optional submit. It does not name or contrast with siblings like click or evaluate, so the differentiation is only implicit in "multiple ... in a single turn."

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?

"In a single turn" hints that this batches work that would otherwise require several click calls, and the optional submit implies a fill-then-submit flow. But there is no explicit when-to-use/when-not, no mention of prerequisites (process target, page readiness), and no pointer to an alternative for single-field interactions.

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