Skip to main content
Glama
alderban107

hyprland-mcp

by alderban107

get_active_window

Retrieve details about the currently focused window in Hyprland desktop environments to enable automated window management and interaction.

Instructions

Get details about the currently focused window.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The handler for 'get_active_window' queries the Hyprland active window status via hyprctl and returns a formatted string with window details.
    @mcp.tool()
    async def get_active_window() -> str:
        """Get details about the currently focused window."""
        w = await hyprctl.query("activewindow")
        if not w or not w.get("class"):
            return "No window is currently focused."
        return (
            f"Active window: [{w['class']}] \"{w['title']}\"\n"
            f"Size: {w['size'][0]}x{w['size'][1]}, Position: ({w['at'][0]},{w['at'][1]})\n"
            f"Workspace: {w['workspace']['name']}, Monitor: {w['monitor']}\n"
            f"Floating: {w['floating']}, Fullscreen: {w['fullscreen']}"
        )
Behavior2/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 states the tool retrieves details but doesn't disclose behavioral traits such as what specific details are returned, error conditions, permissions required, or performance characteristics. This leaves significant gaps for a tool with no 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 a single, clear sentence that efficiently conveys the core purpose without unnecessary words. It is appropriately sized and front-loaded, making it easy to understand at a glance.

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 simplicity (0 parameters, output schema provided), the description is minimally adequate. However, with no annotations and an output schema that likely defines return values, the description could benefit from more context on what 'details' include or usage scenarios, leaving room for improvement.

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 information is needed. The description doesn't add parameter semantics, but this is acceptable given the lack of parameters, warranting a baseline score of 4.

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 ('Get details about') and resource ('the currently focused window'). It distinguishes itself from siblings like 'list_windows' or 'focus_window' by targeting only the active window, though it doesn't explicitly contrast with them.

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 when details about the active window are needed, but it doesn't provide explicit guidance on when to use this tool versus alternatives like 'list_windows' or 'focus_window'. No exclusions or prerequisites are mentioned.

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