Skip to main content
Glama
Electron Debug MCP Server

Electron Debug MCP Server

by amafjarkasi

responsive_theme_matrix

Read-only

Run responsive checks across themes and viewport sizes to verify UI layout, detect text clipping or horizontal overflow, and capture screenshot artifacts.

Instructions

Run a multi-theme (dark/light) and multi-viewport responsive sweep, verifying UI layout, detecting text clipping/horizontal overflow, and capturing screenshot artifacts.

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": "responsive_theme_matrix"
  }
}

Input Schema

NameRequiredDescriptionDefault
themesNoThemes to test (default ['light', 'dark'])
targetIdNo
processIdNoTarget process ID. Omit if only one app is running.
viewportsNoViewport dimensions to test (default 800x600, 1280x800, 1920x1080)
checkOverflowNoWhether to detect elements overflowing viewport bounds (default true)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.15.1

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, so the safety profile is covered. The description adds real context beyond that -- it discloses that the tool produces screenshot artifacts and performs multi-theme/multi-viewport traversal -- but says nothing about runtime cost, how findings or artifacts are returned, or whether failures abort the sweep.

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?

One front-loaded sentence that packs the operation, its dimensions, and its checks with no filler or redundancy. Nothing needs trimming.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a zero-required-parameter, five-parameter tool with no output schema, the description covers what is tested and that artifacts are captured, which is enough to call it correctly. The main residual gap is how results (pass/fail findings vs. image artifacts) are surfaced, but the scope is otherwise well set.

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 description coverage is 80%, so the schema already documents themes, viewports, processId, and checkOverflow defaults. The description reinforces the theme (dark/light) and viewport dimensions but adds no format guidance, and never mentions targetId or processId, leaving the description's marginal value modest.

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 gives a specific verb and resource ('Run a multi-theme ... and multi-viewport responsive sweep') and enumerates the checks performed (layout verification, text clipping, horizontal overflow, screenshots), which distinguishes it from generic capture or assertion siblings. It stops short of naming a sibling to route away from.

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 capability list: an agent can infer this is the tool for responsive/dark-mode sweeps, but there is no explicit when-to-use vs. when-not guidance, no mention of prerequisites, and no pointer to alternatives such as screenshot, diff_screenshot, or assert_ui.

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