Skip to main content
Glama
cmeans

mcp-clipboard

by cmeans
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

clipboard_read_raw

Read-onlyIdempotent

Reads raw clipboard content in a specified MIME format without parsing. Diagnostic only; use clipboard_paste for normal access.

Instructions

Read raw clipboard content in a specific MIME format. Diagnostic tool only — use clipboard_paste instead for normal clipboard access.

This tool returns the clipboard content as-is without any parsing or restructuring. Use clipboard_list_formats first to see what MIME types are available.

Supports any non-binary MIME type. The most common values are text/* types, plus image/svg+xml (text-readable despite the image/ prefix). application/* types pass through as well (application/json, application/xml, application/xhtml+xml, etc.) because the only blocked prefixes are image/, audio/, video/, and the exact type application/octet-stream. Binary MIME types are rejected; use clipboard_paste for images.

Args: mime_type: The MIME type to read from the clipboard. Common values: "text/plain", "text/html", "image/svg+xml", "application/json" selection: Which buffer to read. Defaults to "clipboard". Pass "primary" to read the X11/Wayland PRIMARY selection (middle-click buffer). macOS and Windows have no PRIMARY analog and will return an error if "primary" is passed.

Returns: The raw clipboard content in the requested format, or an error message.

Input Schema

NameRequiredDescriptionDefault
mime_typeNotext/plain
selectionNoclipboard

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.6.2
    • addedInput schema / properties / selection
      Added value: +{
+  "default": "clipboard",
+  "title": "Selection",
+  "type": "string"
+}
  2. First observedv1.0.1

TDQS

A4.9/5.0
Behavior5/5

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

Annotations cover safety (readOnly, idempotent, non-destructive), and the description adds substantial behavioral context beyond them: which MIME prefixes are accepted vs. blocked (image/, audio/, video/, application/octet-stream), that binary is rejected, that content is returned unparsed, and that 'primary' errors on macOS/Windows.

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 purpose and routing, then cleanly structured Args/Returns. Every sentence is useful, though the common MIME values are effectively stated twice (prose and Args), a minor redundancy.

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?

Given a rich output schema and full annotations, the description still covers the gaps that matter: accepted/rejected MIME types, error conditions, and platform constraints. Nothing an agent needs to invoke 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 coverage is 0%, so the description carries full burden and does so thoroughly: it names common mime_type values, explains the text/* vs image/svg+xml vs application/* distinction, and documents the selection parameter's default and platform-specific 'primary' behavior.

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 ('Read raw clipboard content in a specific MIME format') and immediately positions itself against the sibling 'clipboard_paste' as a diagnostic-only tool. An agent can distinguish it from clipboard_paste 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?

Explicit routing guidance: use clipboard_paste for normal access, clipboard_list_formats first to discover MIME types, and clipboard_paste for images. It states both when to use this tool and when to prefer alternatives, with the conditions spelled out.

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