Skip to main content
Glama

Clipboard Read

clipboard_read
Read-onlyIdempotent

Reads current text contents from the Wayland clipboard so AI agents can inspect copied data during desktop automation and testing.

Instructions

Reads current text contents from the Wayland 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": "clipboard_read"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered. The description adds genuine context beyond that: it is Wayland-specific and limited to text payloads, which tells the agent what it will not get back. It does not state what happens on an empty clipboard or when an image/other MIME type is present, leaving failure behavior undisclosed.

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?

A single front-loaded sentence with no filler, hedging, or redundant restatement of the title. Every clause (read, current, text, Wayland) carries information.

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

Completeness4/5

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

With an output schema covering return values, rich annotations, and no parameters, the description needs only to set scope and platform context, which it does. The remaining gap is edge-case behavior (empty clipboard, non-text content) on an otherwise very simple tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

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

The tool takes zero parameters, so there is no argument semantics for the description to explain and the baseline of 4 applies. Nothing about the input contract is misrepresented.

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?

Specific verb plus resource ('Reads current text contents') and an explicit environment qualifier (the Wayland clipboard). An agent can distinguish it from clipboard_write on the read/write axis, though the description never names the sibling or states the inverse operation.

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?

Usage is only implied by the tool name and the word 'current'; there is no explicit when-to-use, when-not-to-use, or routing statement toward clipboard_write or other siblings. The 'text contents' phrasing does implicitly signal that non-text clipboard formats are out of scope, which is the only guidance present.

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