Skip to main content
Glama

desktop_clipboard_set

Writes text, PNG images, or file references to the desktop clipboard, enabling MCP clients to prepare content for paste actions.

Instructions

agent-desktop clipboard-set: Write text to the clipboard

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_set"
  }
}

Input Schema

NameRequiredDescriptionDefault
textNoText to write to the clipboard (ignored if --image or --file-url is given)
imageNoPath to a PNG file to write to the clipboard
file_urlNoFile path to write to the clipboard as a file reference; repeatable

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, yet it says nothing about overwriting existing clipboard contents, platform/permission requirements, or what is returned on success. For a mutation tool with zero annotation coverage this is a significant 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?

Very short and front-loaded with the action, with no filler sentences. The "agent-desktop clipboard-set:" prefix largely restates the tool name and is the only wasted token.

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?

Given a mutation tool with no annotations, no output schema, and multiple mutually exclusive input modes, the description is too thin. It should at minimum note that writing replaces existing clipboard content and that image/file_url modes exist.

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 all three parameters (text, image, file_url) are already documented in the schema, making 3 the baseline. The description adds no semantics beyond restating "text" and in fact omits the image and file modes, so it contributes nothing extra.

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 text to the clipboard"), which distinguishes it from desktop_clipboard_get and desktop_clipboard_clear by implication. However, it claims the tool only writes "text" while the schema accepts image and file_url, so the stated purpose understates the actual scope.

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?

No when-to-use guidance, no prerequisites, and no mention of alternatives such as desktop_set_value or the related clipboard clear/get tools. The agent must infer entirely from the name when this is the right tool.

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