Skip to main content
Glama
Electron Debug MCP Server

Electron Debug MCP Server

by amafjarkasi

get_logs

Read-only

Retrieve captured stdout and stderr logs from a managed Electron process to diagnose runtime issues, with an optional tail limit for recent log chunks.

Instructions

Get captured stdout/stderr logs for a managed Electron process

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": {
      "processId": "<processId>"
    },
    "name": "get_logs"
  }
}

Input Schema

NameRequiredDescriptionDefault
tailNoOptional number of trailing log chunks to return
processIdYesProcess id returned by start_app or attach

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.15.1

TDQS

A3.5/5.0
Behavior3/5

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

With readOnlyHint=true the safety profile is already covered by annotations, so the description only needs to add operational context. It does add that output is *captured* (i.e., buffered) and limited to managed processes, but says nothing about buffer size, truncation, whether reading is destructive, or what a 'log chunk' looks like.

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?

A single front-loaded sentence with zero filler; the verb, resource, and scope all arrive before any caveat. Nothing in the text could be removed without losing information.

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 simple two-parameter read tool this covers the essentials, but with no output schema the description should at least sketch the return shape (chunk list, ordering, whether stdout and stderr are interleaved). Buffer/truncation behavior is also left unstated, which matters for a log-retrieval tool.

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 100%, so both `processId` and `tail` are already documented in the schema, including that `tail` limits trailing chunks. The description adds no syntax, default, or ordering guidance beyond that, so the baseline of 3 applies.

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?

States a specific verb ('Get') and resource ('captured stdout/stderr logs') scoped to 'a managed Electron process', which clearly separates it from console-message, IPC, or network log getters. It stops short of naming a sibling explicitly, so an agent must infer the stdout/stderr vs console-messages distinction from the wording alone.

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: an agent can infer this is for inspecting process output rather than browser-level console output, but there is no explicit when-to-use, when-not-to-use, or named alternative (e.g. get_console_messages). No prerequisites such as needing an attached process are stated beyond the 'managed Electron process' phrasing.

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