Skip to main content
Glama
Electron Debug MCP Server

Electron Debug MCP Server

by amafjarkasi

act_and_verify

Performs a UI action, waits for network idle, then verifies a UI assertion and captures a screenshot automatically when verification fails.

Instructions

Composite action & assertion: performs a UI action (click, click_ax, type_text, type_ax), waits for network idle, verifies assertion (assert_ui), and captures a screenshot immediately if assertion fails.

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": {
      "action": "<action>",
      "assertion": "<assertion>"
    },
    "name": "act_and_verify"
  }
}

Input Schema

NameRequiredDescriptionDefault
actionYes
targetIdNo
assertionYes
processIdNoProcess ID. If omitted, uses the single running app.
waitForSelectorNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.15.1

TDQS

B3.3/5.0
Behavior4/5

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

Annotations supply only destructiveHint=false, so the description carries most of the burden and does add real value: it discloses the ordered sequence (act, wait for network idle, assert) and the side effect of capturing a screenshot on assertion failure. Gaps remain around failure semantics, timeouts, and whether the screenshot or error is returned, which matter for a multi-step composite.

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; every clause maps to a real step in the pipeline. It is dense with parenthetical enum lists, which slightly impedes scanning, but nothing is wasted.

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 composite tool with nested objects, five parameters, and no output schema, the description should explain failure behavior, return contents, and selector/wait semantics. It instead covers only the happy-path pipeline, leaving the parameter and outcome contract underspecified.

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 description coverage is only 20%, so the description must compensate, and it largely does not. It restates the action type enum values and names the assertion concept, but says nothing about targetId, waitForSelector, or the nested action/assertion fields (selector, name, role, text, clear, pressEnter, expression, urlIncludes, textIncludes, titleIncludes, selectorHidden).

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 names a specific composite behavior: it enumerates the action variants (click, click_ax, type_text, type_ax), the wait-for-network-idle step, the assertion step (assert_ui), and the failure screenshot. That makes the tool's job unambiguous. It stops short of explicitly contrasting itself with the sibling atomic tools (click, type_ax, assert_ui), so an agent must infer the composite-vs-atomic relationship.

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?

Usage is only implied: the composite flow suggests 'use when you want an action plus verification in one call', but there is no explicit when-to-use statement, no when-not (e.g., when a plain click or type_text suffices), and no mention of the atomic siblings as alternatives. The agent can guess the intent but is not routed.

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