Skip to main content
Glama
alderban107

hyprland-mcp

by alderban107

launch_app

Launch applications on Hyprland desktop environments by executing commands to open programs or files directly from the system.

Instructions

Launch an application (detached, via Hyprland).

Args: command: The command to run (e.g. "firefox", "kitty", "nautilus ~/Documents")

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
commandYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The launch_app tool handler implementation in server.py, which uses hyprctl.dispatch to execute the command.
    @mcp.tool()
    async def launch_app(command: str) -> str:
        """Launch an application (detached, via Hyprland).
    
        Args:
            command: The command to run (e.g. "firefox", "kitty", "nautilus ~/Documents")
        """
        await hyprctl.dispatch("exec", command)
        return f"Launched: {command}"
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 mentions 'detached' and 'via Hyprland', which gives some context about execution behavior, but lacks details on permissions, error handling, or what 'detached' implies (e.g., background process). More behavioral traits would improve transparency.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is front-loaded with the main purpose, followed by a clear 'Args' section. It's efficient with no wasted sentences, though the formatting could be slightly more polished (e.g., integrating the args into a single paragraph).

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 has an output schema (implied by context signals), the description doesn't need to explain return values. However, as a mutation tool with no annotations and minimal behavioral details, it's adequate but leaves gaps in understanding full context like error cases or system dependencies.

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?

Schema description coverage is 0%, but the description compensates by explaining the 'command' parameter with examples ('firefox', 'kitty', 'nautilus ~/Documents'), adding meaningful context beyond the bare schema. With only one parameter, this is sufficient for clarity.

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 action ('Launch an application') and the mechanism ('detached, via Hyprland'), which is specific. However, it doesn't explicitly differentiate from sibling tools like 'focus_window' or 'close_window', which are also window-related but serve different purposes.

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 clarify if this should be used for opening new applications versus focusing existing ones, or how it relates to tools like 'send_shortcut' for launching apps via keyboard shortcuts.

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