Skip to main content
Glama
Electron Debug MCP Server

Electron Debug MCP Server

by amafjarkasi

set_clipboard

Write text or image data URLs to the OS clipboard, optionally targeting a specific Electron process by process ID.

Instructions

Write the OS clipboard. Pass text, imageDataUrl (a data:image/... URL), or both. Requires inspectMain.

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

Input Schema

NameRequiredDescriptionDefault
textNo
processIdNoProcess ID. If omitted, uses the single running app.
imageDataUrlNodata:image/png;base64,... or another image data URL

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.15.1

TDQS

A3.6/5.0
Behavior3/5

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

Annotations only carry destructiveHint=false, so the description has room to add behavior, and "Requires inspectMain" is a genuinely useful prerequisite disclosure. However, it never warns that writing replaces whatever is already on the clipboard, nor what happens when both payload params are omitted.

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?

Three short sentences with the core action front-loaded, then payload guidance, then the prerequisite. No filler or redundancy.

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 three-parameter, no-output write tool this covers the action, accepted payloads, and the enabling prerequisite. The remaining gap is edge-case behavior (no payload supplied, overwrite semantics), which is secondary but not negligible.

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 coverage is 67%, and the description reiterates the text and imageDataUrl meaning ("a data:image/... URL") while clarifying either-or-both is valid, which the schema's zero required fields only implies. The third parameter, processId, is not mentioned in the description, leaving it to the schema's own text.

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 ("Write the OS clipboard") that an agent can cleanly separate from the read-side sibling get_clipboard. It does not name the alternative explicitly, but the write/read distinction is unambiguous from the verb.

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?

"Pass text, imageDataUrl, or both" tells the agent which inputs to supply, and "Requires inspectMain" states a prerequisite for use. There is no guidance on when to prefer this over siblings or what to do if neither payload is provided.

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