Skip to main content
Glama
Electron Debug MCP Server

Electron Debug MCP Server

by amafjarkasi

get_audit_issues

Read-only

Retrieve buffered Chromium audit issues—cookies, CORS, mixed-content, and deprecations—captured since attach for an Electron app.

Instructions

Buffered Chromium Audits issues (cookie/CORS/mixed-content/deprecations) captured since attach

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

Input Schema

NameRequiredDescriptionDefault
tailNo
processIdNoProcess ID. If omitted, uses the single running app.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.15.1

TDQS

B3/5.0
Behavior3/5

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

readOnlyHint=true already tells the agent this is a safe read. The description adds useful lifecycle context — results are buffered and accumulate from the moment of attach — but says nothing about whether reading drains the buffer, whether results are paginated, or how they are ordered.

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 dense sentence with the resource and the category list front-loaded; no filler. It is terse to the point of omitting the verb, but nothing is wasted.

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 no output schema, the description does its part by naming the issue categories returned, but it leaves the return shape, ordering, and the meaning of 'tail' unexplained for a two-parameter tool.

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 50%: processId is documented in the schema, but 'tail' has no description anywhere. The description mentions neither parameter, so it does not compensate for the undocumented 'tail' semantics (presumably a count limit).

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?

Names a specific resource (Chromium audit issues) and enumerates the categories captured (cookie/CORS/mixed-content/deprecations), which distinguishes it from siblings like get_console_messages and get_network_log. The verb is only implied by the tool name, but the scope is clear.

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 phrase 'captured since attach' hints that attach must happen first, but there is no explicit when-to-use guidance, no statement of when to prefer this over get_console_messages or get_network_log, and no exclusions.

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