Skip to main content
Glama
alderban107

hyprland-mcp

by alderban107

clipboard_write

Copy text to the system clipboard for pasting into applications. This tool enables automated text transfer during desktop interactions.

Instructions

Write text to the clipboard.

Args: text: The text to copy to the clipboard

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
textYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The MCP tool registration and entry point for 'clipboard_write' in the server.
    async def clipboard_write(text: str) -> str:
        """Write text to the clipboard.
    
        Args:
            text: The text to copy to the clipboard
        """
        from . import clipboard
        await clipboard.write(text)
        return f"Copied {len(text)} characters to clipboard"
  • The actual implementation of writing to the clipboard using 'wl-copy'.
    async def write(text: str) -> None:
        """Write text to clipboard."""
        require_tool("wl-copy")
        proc = await asyncio.create_subprocess_exec(
            "wl-copy",
            stdin=asyncio.subprocess.PIPE,
            stderr=asyncio.subprocess.PIPE,
        )
        _, stderr = await proc.communicate(input=text.encode())
        if proc.returncode != 0:
            raise ClipboardError(f"wl-copy failed: {stderr.decode().strip()}")
Behavior2/5

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

No annotations are provided, so the description carries full burden. It states the action ('Write text to the clipboard') but lacks behavioral details such as platform dependencies, permissions required, whether it overwrites existing clipboard content, or any rate limits. This is a significant gap for a mutation tool with zero annotation coverage.

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?

The description is extremely concise and front-loaded, with the core purpose in the first sentence and parameter details in a brief 'Args' section. Every sentence earns its place without redundancy, making it efficient for an agent to parse.

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?

Given the tool's low complexity (one parameter) and the presence of an output schema (which handles return values), the description is minimally adequate. However, it lacks context on behavioral aspects like side effects or prerequisites, which are important for a clipboard mutation tool with no annotations.

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 description adds meaningful context for the single parameter 'text' by explaining it's 'The text to copy to the clipboard', which clarifies its purpose beyond the schema's basic type definition. With 0% schema description coverage and only one parameter, this adequately compensates, though it could specify constraints like length limits.

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 clearly states the tool's purpose with a specific verb ('Write') and resource ('text to the clipboard'), making it immediately understandable. However, it doesn't explicitly differentiate from sibling tools like 'clipboard_read' or 'type_text', which would require a 5.

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?

No guidance is provided on when to use this tool versus alternatives. For example, it doesn't mention when to choose 'clipboard_write' over 'type_text' for input operations or how it relates to 'clipboard_read'. This leaves the agent without context for tool selection.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/alderban107/hyprland-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server