Skip to main content
Glama

set_clipboard

Idempotent

Replaces the macOS clipboard contents with specified text, letting you copy new text for immediate pasting.

Instructions

Replace the clipboard with this text.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "text": "<text>"
    },
    "name": "set_clipboard"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYesThe text to put on the clipboard.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations declare readOnlyHint=false and destructiveHint=false, and "replace" adds genuinely new information: the prior clipboard contents are overwritten rather than appended or merged. It stops short of saying the overwrite is unconditional/irreversible or whether the clipboard is system-wide, which would be useful given the replacement semantics.

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?

One short sentence, action-first, with zero filler or redundant restatement. Nothing can be trimmed without losing meaning.

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, no-output, non-open-world tool with annotations covering the safety profile, the description is essentially sufficient. Minor gaps remain around failure behavior and whether replacement is global, but 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.

Parameters3/5

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

Schema coverage is 100% and the sole required parameter is documented in-schema as "The text to put on the clipboard." The description adds no format, encoding, or length details beyond that, so the baseline 3 applies.

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?

"Replace the clipboard with this text" pairs a specific verb with a specific resource, and the word "replace" inherently contrasts with the sibling get_clipboard. It is unambiguous what the tool does, though it never names the read counterpart outright.

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: an agent infers this is for writing/overwriting clipboard contents. There is no explicit statement of when to prefer this over get_clipboard or any caution about when not to call it, but for a single-purpose one-parameter tool the implied scope is clear enough to be workable.

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