Skip to main content
Glama
Electron Debug MCP Server

Electron Debug MCP Server

by amafjarkasi

type_text

Enters text into the focused Electron app element, optionally focusing a CSS selector or accessibility ref first and clearing existing content.

Instructions

Type text into the focused element (optionally click a selector first)

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

Input Schema

NameRequiredDescriptionDefault
refNoOptional accessibility element ref from snapshot
textYes
clearNoIf true and selector/ref is set, clear the field first
selectorNoOptional CSS selector to focus before typing
targetIdNo
processIdNoTarget process ID. Omit if only one app is running.
pressEnterNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.15.1

TDQS

C2.9/5.0
Behavior3/5

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

Beyond the single destructiveHint=false annotation, the description does disclose that typing targets the focused element and that a selector can be clicked first, which is genuine behavioral context. It omits important traits such as whether text appends or replaces existing content, what happens when nothing is focused, and any failure/permission behavior.

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 waste and the primary action stated first. It is efficient but borders on under-specified rather than deliberately concise.

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 7-parameter input tool with no output schema and minimal annotations, the description is too thin: it doesn't explain pressEnter, targetId/processId targeting, or what the call returns. An agent cannot fully predict the effect of optional parameters from this text alone.

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 only 57% across 7 parameters. The description touches only text and selector (and implicitly the click-before-typing behavior already documented in the schema), leaving pressEnter, targetId, ref, clear, and processId undocumented in prose. It adds little meaning beyond structured fields.

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: "Type text into the focused element," plus the optional pre-click behavior. It is clear what the tool does, but it doesn't distinguish itself from siblings like type_ax or fill_form, so an agent must guess which typing tool applies.

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?

The parenthetical "optionally click a selector first" implies a convenience mode, but there is no stated when-to-use vs when-not-to-use guidance and no mention of alternatives such as type_ax or fill_form. The agent has to infer the selection criteria from tool names alone.

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