Skip to main content
Glama

clipboard

Destructive

Reads or replaces copied text on Windows, letting AI agents retrieve the current copy or overwrite it with new text for desktop automation tasks.

Instructions

Read the clipboard text, or replace it with text (that overwrites what the user copied; prefer ui_act type).

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

Input Schema

NameRequiredDescriptionDefault
textNoomit to read

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the mutation risk is flagged structurally. The description earns credit for explaining what is destroyed — 'overwrites what the user copied' — which tells the agent the prior clipboard contents are lost. It does not cover failure modes such as non-text or empty clipboard contents.

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 covering both modes, the destructive consequence, and the alternative. No wasted wording.

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?

For a one-parameter tool with no output schema, the description covers both invocation modes and the destructive side effect. Only minor gaps remain, such as what happens with empty or non-text clipboard content.

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% and the single parameter already documents 'omit to read', so the schema carries most of the meaning. The description restates the read/write duality and adds the overwrite consequence, which is modest added value over 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?

States a specific resource (clipboard text) and both modes concisely: read when no text is supplied, replace when text is supplied. The parenthetical names the sibling ui_act as the preferred path for typing, which helps differentiate it, though it is framed as a preference rather than a scope distinction.

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

Usage Guidelines4/5

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

Gives a concrete when-not hint: 'prefer ui_act type' when the goal is typing text into a UI. It does not spell out when reading the clipboard is preferable to capture/ui_ocr, but the guidance it does provide is explicit and actionable.

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