Skip to main content
Glama
Electron Debug MCP Server

Electron Debug MCP Server

by amafjarkasi

clear_buffers

Destructive

Clear buffered console messages, network events, process logs, IPC data, and audit records for a target Electron process, so debugging output reflects only current activity.

Instructions

Clear buffered console messages, network events, process logs, ipc, and/or audits

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

Input Schema

NameRequiredDescriptionDefault
ipcNo
logsNo
auditsNo
consoleNo
networkNo
processIdNoTarget process ID. Omit if only one app is running.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.15.1

TDQS

B3.2/5.0
Behavior3/5

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

destructiveHint=true already tells the agent this removes data, so the bar is lower; the description adds real value by naming exactly which buffer categories are destroyed. It does not say whether clearing is permanent, whether buffers regrow, or what the default selection is when all flags are omitted.

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 an actual parameter. The 'and/or' construction is slightly loose but costs nothing.

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?

For a 6-parameter destructive mutation with no output schema and sparse schema descriptions, the definition covers the 'what' but not the default-selection semantics or the single-app scoping behavior. An agent can call it, but may be surprised by which buffers actually get cleared.

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 17% (just processId documented), so the description must compensate — and it partly does by mapping console, network, logs, ipc, and audits to human-readable buffer types. However, it never states defaults for these booleans (all false? all true?) nor clarifies the processId scoping beyond the schema's own text.

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 ('Clear') plus an enumerated set of resources (console messages, network events, process logs, ipc, audits), which is far more informative than the bare name. It implicitly distinguishes itself from read-side siblings like get_console_messages by being the clearing operation, though it never names an alternative explicitly.

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?

There is no statement of when to use this versus inspecting buffers first, no prerequisites, and no note about what happens if no flags are supplied. The 'and/or' phrasing hints that callers may clear a subset, but the agent must infer this.

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