Skip to main content
Glama
Electron Debug MCP Server

Electron Debug MCP Server

by amafjarkasi

stop_screencast

Terminates an active screencast and optionally writes the final frame as a PNG or JPEG to a chosen path, preserving the last captured image.

Instructions

Stop screencast; optionally write last frame PNG/JPEG to path

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

Input Schema

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

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?

The single annotation only says readOnlyHint=false, so the description must carry the behavior load. It does disclose the meaningful side effect (writing a frame to a path) and that the frame is the final one, but omits error behavior when nothing is recording and whether the file is overwritten.

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 compact sentence, front-loaded with the primary action and the optional side effect after the semicolon. Nothing extraneous.

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 two-parameter, no-output-schema tool this is nearly complete: both parameters are accounted for and the frame-capture option is explained. Only edge-case behavior (no active screencast, overwrite semantics) is left unstated.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is only 50% — processId is documented there but path is not. The description compensates by explaining that path is the destination for the last frame and that the format is inferred from the extension (PNG/JPEG), which the schema alone does not convey.

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?

A precise verb+resource ('Stop screencast') that pairs naturally with start_screencast among the siblings. The optional file-write outcome is stated too, so the agent knows exactly what the call does without opening the schema.

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 implied by the name and the mention of writing the last frame, but there is no explicit when-to-use guidance, no note about what happens when no screencast is running, and no mention of how processId selection interacts with the call.

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