Skip to main content
Glama
Electron Debug MCP Server

Electron Debug MCP Server

by amafjarkasi

resolve_stack

Read-only

Resolve stack frames to source snippets via Debugger.getScriptSource or file URLs, helping map debugger frames to readable code during Electron debugging.

Instructions

Resolve stack frames to source snippets (Debugger.getScriptSource / file://)

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": {
      "frames": "<frames>"
    },
    "name": "resolve_stack"
  }
}

Input Schema

NameRequiredDescriptionDefault
framesYes
targetIdNo
processIdNoProcess ID. If omitted, uses the single running app.
contextLinesNo

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?

readOnlyHint=true already establishes this as a safe non-mutating read, so the description only needs to add context. It does add one meaningful detail -- sources come from the debugger or file:// -- which hints that frames from scripts with no retrievable source may fail, but it never says so explicitly, nor does it describe partial-failure behavior.

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, and the mechanism parenthetical is placed where it is immediately useful. It is efficient rather than padded, though the terseness borders on under-specification for a tool with a nested required array.

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?

No output schema exists, so the description should say what a resolved frame looks like or what happens when resolution fails, and it does not. Given a complex nested required parameter and debugger-dependent retrieval, a competent agent is left to infer too much about frame addressability and error cases.

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 description coverage is 25% (only processId is documented in the schema), so the description is expected to compensate and does not. The required 'frames' array and its url/scriptId/lineNumber/columnNumber members are never explained, and 'contextLines' (capped at 20) is not mentioned at all, leaving the agent to guess how many surrounding snippet lines to request.

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 names a specific verb ('Resolve') and resource ('stack frames') and states the output ('source snippets'), which is far more informative than the bare tool name. It also names the underlying retrieval path (Debugger.getScriptSource / file://), which clarifies what 'resolve' actually means, though it does nothing to differentiate this from adjacent diagnostic tools.

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 infers this is the tool to call when it has raw stack frames and wants source. There is no statement of when to prefer it, no prerequisites (e.g. does the app need to be paused with a live debugger session?), 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