Skip to main content
Glama
Electron Debug MCP Server

Electron Debug MCP Server

by amafjarkasi

start_screencast

Capture a running Electron app's screen by starting a buffered screencast with configurable format, quality, and frame limits; pair with stop to end capture.

Instructions

Start Page.startScreencast; buffers up to maxFrames (ack frames). Pair with stop_screencast.

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

Input Schema

NameRequiredDescriptionDefault
formatNo
qualityNo
targetIdNo
maxFramesNo
processIdNoProcess ID. If omitted, uses the single running app.
everyNthFrameNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.15.1

TDQS

B3.1/5.0
Behavior3/5

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

Annotations only declare destructiveHint=false, so the description must carry behavior, and it does add that frames are buffered up to maxFrames and that frames are acked. It does not explain what happens when the buffer fills, whether capture continues silently, or how the buffered frames are actually retrieved.

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?

Two short clauses, front-loaded with the action and constraint. The parenthetical "(ack frames)" is terse to the point of ambiguity, but nothing is wasted.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a stateful streaming tool with no output schema, the definition never says how buffered frames reach the caller, nor the consequences of never calling stop_screencast. That missing consumption model is a significant gap for a tool whose whole purpose is producing a stream.

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 coverage is 17% across six parameters, and the description only illuminates maxFrames (buffer cap plus ack semantics). format, quality, everyNthFrame and targetId are left entirely to a bare schema, so the description does not compensate for the low coverage.

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?

Names a specific verb and resource ("Start Page.startScreencast") and states the buffering behavior, which is enough to separate it from stop_screencast. The CDP-domain phrasing is somewhat opaque, but the intent is unambiguous.

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?

"Pair with stop_screencast" gives a clear lifecycle pairing, implying this is the open half of a start/stop session. It stops short of saying when to choose screencasting over a plain screenshot tool (capture_mhtml, diff_screenshot) or what conditions make pairing mandatory.

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