Skip to main content
Glama
Electron Debug MCP Server

Electron Debug MCP Server

by amafjarkasi

type_ax

Focus an accessibility-named field and insert text, with an option to clear existing content first. Use it to target and fill specific Electron UI inputs by name.

Instructions

Focus an element by accessibility name and insert text (optional clear)

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": {
      "name": "<name>",
      "text": "<text>"
    },
    "name": "type_ax"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesAccessible name of the field
roleNoAX role, e.g. "textbox"
textYes
clearNo
exactNo
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

B3.1/5.0
Behavior3/5

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

Annotations supply only destructiveHint=false, and the description does add that the tool focuses the element before typing, which is real behavioral information. It does not say whether text is appended or replaced by default, whether the operation triggers submit/blur handlers, what happens if the element is not found, or any return/failure signal.

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?

One front-loaded sentence with no padding; the action and target lead. The trailing parenthetical '(optional clear)' is slightly cryptic as shorthand but still efficient.

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 seven-parameter, mutating UI action with no output schema and minimal annotations, the description is thin: it omits clear's default, the role/exact/targetId semantics, error behavior, and whether text is appended or replaces. It is enough to guess the call but not enough to call it confidently.

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?

Seven parameters with only 43% schema description coverage, so the description must partly compensate. It clarifies the meaning of 'clear' (clear existing content before inserting), which the schema leaves bare, and 'text' is self-evident. However, 'exact' and 'targetId' remain undocumented in both schema and description, leaving nearly half the surface unexplained.

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: it focuses an accessibility-named element and inserts text into it. That is enough to distinguish it from a generic text-typing tool conceptually, though the sibling name type_text (or type_ax's counterpart) is never named, so sibling differentiation is left implicit.

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 explicit guidance on when to use this instead of type_text, click_ax, or fill_form, and no prerequisites are stated (e.g., the app must be attached/visible). The only hint is the parenthetical '(optional clear)', which is a parameter note rather than a usage rule.

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