Skip to main content
Glama
Electron Debug MCP Server

Electron Debug MCP Server

by amafjarkasi

set_console_live

Toggles live MCP log notifications for Electron console events: enable to stream all console levels as they occur, while errors always notify regardless of the setting.

Instructions

Enable/disable live MCP log notifications for console events (all levels when enabled; errors always notify)

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": {
      "enabled": "<enabled>"
    },
    "name": "set_console_live"
  }
}

Input Schema

NameRequiredDescriptionDefault
enabledYestrue to stream console events as MCP logs

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.15.1

TDQS

A4/5.0
Behavior4/5

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

Annotations only supply destructiveHint=false, so the description carries the behavioral load and does so: it discloses that enabling streams console events at all levels as MCP logs and that error-level events notify regardless of state. It does not say whether the setting persists across sessions or is per-connection, which is the main remaining gap.

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 sentence, front-loaded with the toggled resource, with the conditional caveat in parentheses. No filler and nothing an agent must read past to get the core action.

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 single-boolean toggle with no output schema and minimal annotations, this is nearly complete: what it turns on, what level of events it covers, and the always-on error exception are all present. Only persistence scope and the exact shape of the emitted log entries are unaddressed.

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?

There is a single boolean parameter with 100% schema description coverage ("true to stream console events as MCP logs"), so the schema already documents it fully. The description's "all levels when enabled" adds a little meaning about the effect of true, but nothing about the effect of false beyond disabling.

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?

"Enable/disable live MCP log notifications for console events" states a specific verb pair and resource, and the parenthetical clarifies the scope of what gets streamed. It is clear what the tool does, though it never names get_console_messages as the polling alternative, so sibling differentiation relies on inference from names.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The parenthetical "errors always notify" effectively tells the agent when this tool is unnecessary (you do not need to enable it to see errors) and when it is needed (to stream all levels). There is no explicit when-not-to-use statement or named alternative, so it falls short of a 5.

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