Skip to main content
Glama
alderban107

hyprland-mcp

by alderban107

clipboard_read

Retrieve text content from the system clipboard for integration with desktop automation workflows in Hyprland environments.

Instructions

Read the current clipboard contents as text.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The actual implementation of the clipboard reading logic using wl-paste.
    async def read() -> str:
        """Read clipboard contents as text."""
        require_tool("wl-paste")
        proc = await asyncio.create_subprocess_exec(
            "wl-paste", "-n",
            stdout=asyncio.subprocess.PIPE,
            stderr=asyncio.subprocess.PIPE,
        )
        stdout, stderr = await proc.communicate()
        if proc.returncode != 0:
            raise ClipboardError(f"wl-paste failed: {stderr.decode().strip()}")
        return stdout.decode()
  • MCP tool registration and handler entry point for clipboard_read.
    @mcp.tool()
    async def clipboard_read() -> str:
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It discloses the basic behavior (reading clipboard as text) but does not add context about potential limitations (e.g., platform dependencies, permissions needed, or handling of non-text content). The description is accurate but minimal, offering no extra behavioral traits beyond the core function.

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 a single, efficient sentence with no wasted words. It is front-loaded with the core action and resource, making it easy to understand quickly. Every part of the sentence contributes directly to clarifying the tool's purpose.

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?

Given the tool's simplicity (0 parameters, no annotations, but with an output schema), the description is complete enough for a basic read operation. It specifies the output format ('as text'), and since an output schema exists, detailed return value explanation is unnecessary. However, it could benefit from mentioning any assumptions or constraints, but the gaps are minor.

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 has 0 parameters, and schema description coverage is 100%, so no parameter documentation is needed. The description does not add parameter semantics, but this is acceptable given the lack of parameters, aligning with the baseline of 4 for zero parameters.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the specific action ('Read') and target resource ('current clipboard contents as text'), distinguishing it from sibling tools like clipboard_write (which writes to clipboard) and other unrelated tools. It precisely communicates what the tool does without ambiguity.

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?

The description implies usage context by specifying 'current clipboard contents,' suggesting it retrieves whatever is currently copied. However, it does not explicitly state when to use this tool versus alternatives (e.g., if there are other clipboard-related tools beyond clipboard_write) or any prerequisites, so it lacks explicit exclusions or comparisons.

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