Skip to main content
Glama
alderban107

hyprland-mcp

by alderban107

list_monitors

Retrieve connected monitor details including resolution, position, and active workspace for managing multi-display setups in Hyprland desktop environments.

Instructions

List all connected monitors with resolution, position, and active workspace.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • Implementation of the list_monitors tool. It uses hyprctl.query("monitors") to fetch monitor data and formats it into a human-readable string.
    @mcp.tool()
    async def list_monitors() -> str:
        """List all connected monitors with resolution, position, and active workspace."""
        monitors = await hyprctl.query("monitors")
        lines = []
        for m in monitors:
            lines.append(
                f"- {m['name']}: {m['width']}x{m['height']}@{m['refreshRate']:.0f}Hz "
                f"at ({m['x']},{m['y']}), workspace {m['activeWorkspace']['name']}"
                f"{' [focused]' if m.get('focused') else ''}"
            )
        return "\n".join(lines)
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. While it indicates this is a read operation ('List'), it doesn't mention potential side effects, permissions needed, rate limits, or what format the output takes. The description is minimal and lacks behavioral context beyond the basic action.

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 zero wasted words. It's front-loaded with the core action and immediately specifies the returned data attributes. Every element earns its place.

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, read-only operation) and the presence of an output schema, the description is reasonably complete. It specifies what data will be returned, though it could benefit from more behavioral context about how the data is structured or formatted.

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 with 100% schema description coverage, so the schema already fully documents the parameter situation. The description appropriately doesn't discuss parameters since none exist, maintaining focus on what the tool does rather than what it accepts.

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 ('List all connected monitors') and specifies the exact data returned ('with resolution, position, and active workspace'). It distinguishes itself from siblings like 'list_windows' and 'list_workspaces' by focusing exclusively on monitor hardware.

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 context (when you need monitor information) but doesn't explicitly state when to use this tool versus alternatives like 'get_active_window' or 'screenshot'. No guidance on prerequisites or exclusions is provided.

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