Skip to main content
Glama
alderban107

hyprland-mcp

by alderban107

mouse_move

Move the mouse cursor to precise screen coordinates using Hyprland's native movecursor for pixel-accurate positioning without acceleration issues.

Instructions

Move the mouse cursor to absolute layout coordinates.

Uses Hyprland's native movecursor — pixel-accurate, no acceleration issues.

Args: x: Target X coordinate y: Target Y coordinate

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
xYes
yYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The MCP tool definition for `mouse_move` in `server.py`, which calls the helper function.
    @mcp.tool()
    async def mouse_move(x: int, y: int) -> str:
        """Move the mouse cursor to absolute layout coordinates.
    
        Uses Hyprland's native movecursor — pixel-accurate, no acceleration issues.
    
        Args:
            x: Target X coordinate
            y: Target Y coordinate
        """
        from . import input as inp
        await inp.move_cursor(x, y)
        return f"Moved cursor to ({x}, {y})"
  • The helper function `move_cursor` in `input.py` that executes the `movecursor` dispatch command via `hyprctl`.
    async def move_cursor(x: int, y: int) -> None:
        """Move cursor to absolute coordinates using Hyprland's native movecursor."""
        await hyprctl.dispatch("movecursor", f"{x} {y}")
Behavior4/5

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

With no annotations provided, the description carries full burden and adds valuable behavioral context: it specifies 'pixel-accurate' precision, mentions 'no acceleration issues,' and identifies the underlying implementation (Hyprland's native movecursor). However, it doesn't disclose potential side effects, error conditions, or performance characteristics.

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 perfectly front-loaded with the core purpose in the first sentence, followed by implementation details and parameter explanations. Every sentence earns its place with no wasted words, and the structure (purpose → behavior → parameters) is logical and efficient.

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 moderate complexity (2 simple parameters), no annotations, and the presence of an output schema (which handles return values), the description is mostly complete. It covers purpose, behavior, and parameters well, though it could benefit from mentioning coordinate system origin or screen boundaries for full completeness.

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?

With 0% schema description coverage, the description compensates by clearly explaining both parameters: 'x: Target X coordinate' and 'y: Target Y coordinate.' It adds meaning beyond the bare schema by specifying these are 'absolute layout coordinates' and 'target' positions, though it doesn't provide coordinate system details or range constraints.

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 ('Move the mouse cursor') and target ('to absolute layout coordinates'), distinguishing it from siblings like mouse_click or mouse_drag. It uses precise language that leaves no ambiguity about what the tool does.

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?

The description implies usage for pixel-accurate cursor movement without acceleration, but doesn't explicitly state when to use this versus alternatives like mouse_drag or mouse_click. It mentions Hyprland's native implementation, which provides some context but no explicit guidance on 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