Skip to main content
Glama
Electron Debug MCP Server

Electron Debug MCP Server

by amafjarkasi

get_clipboard

Read-only

Reads the OS clipboard to return text and, when present, a PNG imageDataUrl for Electron debugging; requires inspectMain.

Instructions

Read the OS clipboard. Returns text and, when present, imageDataUrl (PNG). 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": "get_clipboard"
  }
}

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.15.1

TDQS

A3.9/5.0
Behavior4/5

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

readOnlyHint=true already establishes the safety profile, so the description's added value is real: it discloses the return shape (text, and imageDataUrl as PNG only when an image is present) and an authorization prerequisite (inspectMain). That goes beyond what the annotation declares; only pagination/size limits or failure behavior are left unstated.

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?

Two compact sentences, front-loaded with the action and immediately followed by the return contract and the prerequisite. No filler and nothing that restates structured fields verbatim.

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

Completeness5/5

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

For a single-parameter read-only tool with no output schema, the description covers the action, the return payload (including the conditional image case), and the access prerequisite. Nothing an agent needs in order to call it correctly is missing.

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 100%, so processId and its default ("single running app" when omitted) are already documented in the schema. The description adds nothing about processId, which is acceptable given the baseline, but it also does not clarify what happens with multiple running apps.

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?

"Read the OS clipboard" names a specific verb and resource, and the return payload (text plus optional imageDataUrl PNG) makes the scope concrete. It is naturally distinguishable from the sibling set_clipboard by the read/write verb contrast, though it never names the alternative explicitly.

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?

The description supplies a prerequisite ("Requires inspectMain") but gives no explicit when-to-use or when-not-to-use guidance, and does not point to set_clipboard as the mutation counterpart. Usage is only implied by the read framing.

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