Skip to main content
Glama
Sign In
Copilot Desktop MCP

Copilot Desktop MCP

by avianhermana
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Set Clipboard

set_clipboard

Copies provided text to the Windows clipboard, enabling AI assistants to transfer generated or retrieved content for immediate pasting into other applications.

Instructions

Copy the given text into the Windows clipboard.

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
textYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.3/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full behavioral burden. It does convey the key side effect implicitly (system clipboard content is replaced by the given text) and pins the platform to Windows, but it never states that existing clipboard contents are overwritten, nor any size limits or failure modes such as a locked clipboard.

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 zero wasted wording. Nothing is buried and there is no filler.

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

Completeness3/5

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

For a one-parameter clipboard-write tool with an output schema, the description covers the core operation adequately. It omits the destructive-overwrite behavior and error conditions, which are the only meaningful gaps given how simple the tool is.

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 description coverage is 0% for the single 'text' parameter, but the description's phrase 'the given text' maps directly onto it and the name is self-explanatory. No constraints (empty string, length, encoding) are added beyond the bare string type in 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?

The description names a specific verb ('Copy') and a specific resource ('the Windows clipboard'), so an agent immediately knows this is a clipboard-write operation. It does not differentiate from the sibling get_clipboard, but the purpose itself is unambiguous.

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

Usage Guidelines2/5

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

There is no guidance on when to use this tool versus alternatives, and the obvious counterpart get_clipboard is not referenced. The agent must infer usage entirely from the verb.

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