Skip to main content
Glama
IlyasKhallouki

hypruse

by IlyasKhallouki
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

launch

Destructive

Open a desktop app by running a Hyprland command, optionally placing its window on a chosen workspace or in the background while waiting for it to appear.

Instructions

Open an app: run command via Hyprland exec. Optional workspace placement (silent, works even for single-instance apps like browsers, whose window gets moved after it appears) and wait_s (1-30, default 8; raise for slow apps). Without workspace, the app opens silently on the next of the agent's own workspaces (HYPRUSE_AGENT_WORKSPACES, 99 down to 90 by default) that is not on screen, so the agent can work on it in the background; background=false opens it on the human's workspace instead. It waits for its own window (one on that workspace, or of the program's own class), never one the human opens meanwhile. An app that is already running opens its window from the running process, on the human's screen, before it is moved: the note says so. Returns the new window's address/class/title/workspace, or a timeout note.

Input Schema

NameRequiredDescriptionDefault
wait_sNo
commandYes
workspaceNo
backgroundNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.13.0
    • addedInput schema / properties / background
      Added value: +{
+  "anyOf": [
+    {
+      "type": "boolean"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Background"
+}
  2. Addedv0.11.0
  3. Removedv0.9.4
  4. First observedv0.1.1

TDQS

A4.7/5.0
Behavior5/5

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

Far exceeds what annotations provide: it discloses silent background launching, single-instance app window-moving behavior, that it waits only for its own window and never one the human opens, and the timeout outcome. This is unusually rich behavioral context for a mutation tool.

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?

Front-loaded with the core action, and each sentence carries real information. However the single dense paragraph is long and slightly run-on, revisiting workspace placement behavior more than once.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a behaviorally complex launcher, the description covers the mechanism, placement logic, waiting semantics, edge cases, and even the return values (which the output schema already supplies). Nothing essential for correct invocation is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Despite 0% schema description coverage, the description fully annotates all four params: command semantics, workspace placement effect, wait_s range (1-30, default 8) and when to raise it, and the meaning of background. It compensates completely for the empty schema.

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?

States a specific verb+resource ('Open an app') and the exact mechanism ('run `command` via Hyprland exec'). An agent can distinguish this from siblings like screenshot, click_ui, or keyboard 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?

Gives clear conditional guidance for each option: use `workspace` for silent placement, raise `wait_s` for slow apps, set `background=false` to open on the human's workspace. It stops short of explicitly naming or excluding sibling tools, so no full routing guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools