Skip to main content
Glama

desktop_clipboard_get

Reads plain-text, image, or file-URL clipboard contents so MCP clients can inspect what the user copied and use it in desktop workflows.

Instructions

agent-desktop clipboard-get: Read plain-text or typed clipboard contents

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

Input Schema

NameRequiredDescriptionDefault
outNoWhere to write image content; defaults to a private temp file under the session dir
formatNoClipboard format to read: text (default), auto, image, file-urls

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden, and it discloses almost nothing: it implies a non-destructive read but says nothing about permission/accessibility requirements, empty-clipboard or error behavior, or that image reads produce a file on disk (covered only in the schema parameter text). For a tool with zero annotation coverage this is a meaningful gap.

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?

It is a single short, front-loaded line with no filler. The only waste is the 'agent-desktop clipboard-get:' prefix, which restates the tool name and title rather than adding information.

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?

The tool is simple with two optional, fully documented parameters, but with no output schema the description should say what is returned (clipboard text vs. a file path for image output) and what happens when the clipboard is empty. It is minimally adequate rather than complete.

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 100%, so both 'out' and 'format' are already fully documented, setting the baseline at 3. The phrase 'plain-text or typed' loosely echoes the format enum but adds no syntax, default, or interaction detail beyond the schema.

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?

The description gives a specific verb ('Read') and resource ('clipboard contents') and scopes it to 'plain-text or typed' formats, which separates it from desktop_clipboard_set and desktop_clipboard_clear by action. It is clear what the tool does, though it never names those siblings explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use guidance, no prerequisites, and no mention of alternatives such as the set/clear clipboard siblings. Usage is only inferable from the tool name and the word 'Read'.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.