Skip to main content
Glama
IlyasKhallouki

hypruse

by IlyasKhallouki
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

hypr

Control Hyprland windows and workspaces over IPC. Switch workspaces, focus, move, close, fullscreen, or toggle floating windows with direct commands.

Instructions

Window/workspace ops over IPC (instant, no vision). action='workspace' (workspace: number/name/'special:name') | 'focus_window' (target: address) | 'move_window' (target + workspace, silent) | 'close_window' (target) | 'fullscreen' (target?) | 'toggle_floating' (target?). then ('desktop'|'screenshot'|'ui'|'none') appends the result to this call.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
thenNonone
actionYes
targetNo
workspaceNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.11.0
  2. Removedv0.9.4
  3. Changed3 schema fields changedv0.5.0
    • addedInput schema / properties / then
      Added value: +{
+  "default": "none",
+  "title": "Then",
+  "type": "string"
+}
    • addedOutput schema / properties / result / anyOf
      Added value: +[
+  {
+    "items": {},
+    "type": "array"
+  },
+  {
+    "type": "string"
+  }
+]
    • removedOutput schema / properties / result / type
      Removed value: -"string"
  4. First observedv0.1.1

TDQS

A4.3/5.0
Behavior3/5

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

With no annotations, the description carries the burden of behavioral disclosure. It does add useful traits: 'instant, no vision', move_window is 'silent', and `then` 'appends the result to this call'. However, it does not disclose failure behavior, permissions, or irreversible effects of close_window/fullscreen/toggle_floating beyond the action names themselves.

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 compact and dense with no filler. Main domain is front-loaded, action alternatives are presented in an unambiguous pipe notation, and the trailing `then` sentence covers chaining semantics in one line.

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?

For a multi-action IPC tool with no schema descriptions and no annotations, the description covers actions, parameter formats, and chaining. It doesn't elaborate on address format or failure/error cases, but the presence of an output schema means return-value details are not strictly necessary.

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?

Schema properties have no descriptions (0% coverage), and the description fully compensates by mapping each action to its parameters: workspace accepts number/name/'special:name', target is an address, and then has valid values 'desktop'|'screenshot'|'ui'|'none'. This makes the bare schema actionable.

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 opening line 'Window/workspace ops over IPC (instant, no vision)' names the resource domain and adds a distinguishing mechanism, and the action list gives concrete verbs: workspace, focus_window, move_window, close_window, fullscreen, toggle_floating. This separates it from siblings like ui/click_ui/screenshot, which rely on vision.

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?

The phrase 'over IPC (instant, no vision)' clearly sets context for direct window manager operations without visual processing, which implies using this rather than vision-based siblings. It does not explicitly name alternatives or say when not to use it, so it stops short of full when/when-not 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