Skip to main content
Glama
Electron Debug MCP Server

Electron Debug MCP Server

by amafjarkasi

get_response_body

Read-only

Fetches the response body for a buffered network request ID after Network.loadingFinished, enabling inspection of captured Electron app network responses.

Instructions

Fetch body for a buffered network requestId (call after Network.loadingFinished)

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": {
      "requestId": "<requestId>"
    },
    "name": "get_response_body"
  }
}

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.15.1

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, so safety is covered. The description adds the meaningful behavioral constraint that only buffered requests have retrievable bodies and that the call must follow loading completion, but it is silent on failure behavior (error when unbuffered) and on the encoding/truncation of the returned body.

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 compact sentence with the timing prerequisite front-loaded in parentheses. No filler, and the most failure-prone detail is positioned where it will be read first.

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?

There is no output schema, so the description remains the only source for what comes back, yet it never indicates whether the body is text, base64, or possibly truncated. For a tool whose entire value is a returned payload, that is a notable omission at this parameter coverage.

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 33%, so the schema covers only processId; targetId and requestId carry no descriptions there. The description adds the key qualifier that requestId must refer to a buffered request, but says nothing about targetId or which app/process combination is needed when multiple are attached.

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 and resource ('Fetch body') and narrows the scope to 'a buffered network requestId', which separates it from the broader network-inspection siblings such as get_network_log. It stops short of naming an alternative tool, but the 'buffered' qualifier makes the intended target unambiguous.

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 'call after Network.loadingFinished' gives an explicit ordering prerequisite, which is real when-to-use guidance an agent would otherwise get wrong. It does not say what to do if the request was never buffered or how to obtain a requestId in the first place.

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