Skip to main content
Glama
cmeans

mcp-clipboard

by cmeans
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

clipboard_copy

DestructiveIdempotent

Copy text or formatted content to the system clipboard, replacing current contents so you can paste it into other applications.

Instructions

Copy text to the user's system clipboard. Replaces whatever is currently on the clipboard with the provided content.

WHEN TO CALL THIS TOOL:

Call this tool when the user says "copy this", "put this on my clipboard", "copy to clipboard", "send to clipboard", or any phrase that implies writing content to the clipboard.

Also call this tool when you have produced formatted output (cleaned-up JSON, a markdown table, reformatted code, an HTML table, etc.) and the user wants to use it outside the conversation — copying to clipboard lets them paste it elsewhere.

Args: content: The text to place on the clipboard. Any string is accepted. mime_type: MIME type for the clipboard content (default: "text/plain"). Use "text/html" to write HTML that applications can paste as rich text. Use "text/rtf" to write RTF content. Use "image/svg+xml" to write an SVG; SVG is XML, so it rides this text-write path rather than clipboard_copy_image. Binary image MIME types (image/png, image/jpeg, etc.) and audio/* / video/* are rejected — for PNG or JPEG, use clipboard_copy_image. Note: On Wayland and X11, any text/* MIME type is accepted, plus image/svg+xml. On macOS and Windows, only text/plain, text/html, text/rtf, and image/svg+xml are supported.

Returns: A confirmation message with the number of characters copied and the MIME type written.

Input Schema

NameRequiredDescriptionDefault
contentYes
mime_typeNotext/plain

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.6.2
    • addedInput schema / properties / mime_type
      Added value: +{
+  "default": "text/plain",
+  "title": "Mime Type",
+  "type": "string"
+}
  2. First observedv1.0.1

TDQS

A4.5/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, idempotentHint=true, and readOnlyHint=false, so the mutation profile is known. The description adds genuine context beyond that: it explains WHAT is destroyed ('replaces whatever is currently on the clipboard'), the platform-dependent MIME support (Wayland/X11 vs macOS/Windows), and which MIME types are rejected. This is useful added detail rather than repetition of annotations.

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?

Front-loaded with the core action and organized under clear WHEN TO CALL / Args / Returns headers, so an agent can scan it quickly. It is thorough to the point of being slightly verbose (the trigger-phrase enumeration and per-platform MIME notes), but every section maps to a real decision the caller must make.

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 two-parameter mutation tool, the description covers the action, the destructive effect, trigger conditions, sibling routing, parameter formats, and platform constraints. An output schema exists, yet the Returns section still summarizes the confirmation shape, so nothing needed 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.

Parameters5/5

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

Schema description coverage is 0%, so the description carries the full burden and does so: it documents that content accepts any string, gives mime_type's default, enumerates supported values (text/plain, text/html, text/rtf, image/svg+xml), and explains the rejection of binary/audio/video types with the correct fallback tool.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Copy text to the user's system clipboard') and immediately distinguishes it from siblings by naming clipboard_copy_image as the path for binary image types. An agent can tell this apart from clipboard_copy_markdown, clipboard_paste, and clipboard_read_raw without opening any schema.

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

Usage Guidelines5/5

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

An explicit WHEN TO CALL section lists trigger phrases ('copy this', 'put this on my clipboard') plus the proactive case (formatted output the user wants outside the conversation). It also names the alternative tool and the exact condition that selects it ('for PNG or JPEG, use clipboard_copy_image'), leaving nothing to inference.

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