Skip to main content
Glama
Electron Debug MCP Server

Electron Debug MCP Server

by amafjarkasi

assert_ui

Read-only

Verifies URL, title, text, selector, console-error budget, or JS expression in an Electron app, returning per-check pass/fail details without throwing on failed checks.

Instructions

Check url/title/text/selector/console-error budget/expression. Returns pass:false with per-check detail (does not throw on a failed check).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "assert_ui"
  }
}

Input Schema

NameRequiredDescriptionDefault
selectorNo
targetIdNo
processIdNoTarget process ID. Omit if only one app is running.
expressionNoJS expression that must be truthy
urlIncludesNo
textIncludesNo
titleIncludesNo
selectorHiddenNo
maxConsoleErrorsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.15.1

TDQS

B3.4/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=true, so the non-mutating nature is covered. The description does add one genuinely valuable behavioral fact: it returns pass:false with per-check detail and does not throw on a failed check, which prevents an agent from treating a failed assertion as an error. It says nothing about how conditions combine, what happens with zero conditions supplied, or timeout 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?

Two short sentences, front-loaded with the checkable conditions and followed immediately by the return contract. No filler, though the extreme terseness is part of why the combination semantics go unstated.

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?

With 9 optional parameters, low schema coverage, no output schema, and high behavioral nuance, this is a fairly complex tool. The description covers the return shape at a high level but omits how the checks compose, which is the single most important thing an agent needs to call it correctly.

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 only 22%, so the description must carry more weight; it does map most parameters to check types (urlIncludes, titleIncludes, textIncludes, selector, maxConsoleErrors, expression). However it leaves selectorHidden and targetId unexplained and does not clarify matching semantics (substring vs exact) or whether all conditions must hold simultaneously.

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 uses a concrete verb ('Check') and enumerates the resources being asserted against: url, title, text, selector, console-error budget, and expression. An agent can tell this is a multi-condition assertion tool rather than a general evaluator, though it never names a sibling like 'evaluate' or 'get_console_messages' to sharpen the boundary.

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 by the verb 'Check' and by the fact that several conditions can be combined in one call. There is no explicit when-to-use versus when-to-use-something-else guidance, no statement about whether multiple supplied checks are ANDed, and no prerequisites such as needing an attached target.

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