Skip to main content
Glama

hypr

Destructive

Control Hyprland windows and workspaces via IPC: focus, move, close, fullscreen, toggle floating. For AI agents managing Wayland desktop without vision.

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. While the background guarantee is on (HYPRUSE_BACKGROUND=1), workspace, focus_window and fullscreen are refused because they change the human's view, and move_window moves only to the agent's own workspaces.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "action": "<action>"
    },
    "name": "hypr"
  }
}

Input Schema

NameRequiredDescriptionDefault
thenNonone
actionYes
targetNo
workspaceNo

Output 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/5.0
Behavior4/5

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

Annotations cover the safety profile (readOnlyHint=false, destructiveHint=true), and the description adds real context beyond that: the background-mode refusal rules, the workspace confinement of move_window, the 'silent' move, and how 'then' appends output to the call. It stops short of saying which actions are irreversible or what closing a window loses.

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-loads the instant/no-vision premise, then uses a compact pipe-delimited action list, then appends the constraint sentence last. Dense but every clause carries information; the backtick/pipe notation is scannable rather than wasteful.

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 an output schema (so return values need not be explained), the description covers the action vocabulary, the shared parameters, and the environment-dependent refusals. Nothing critical is missing, though the dispatch rules between hypr and its ui/desktop siblings remain implicit.

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 coverage is 0% and the schema has no enums, so the description carries the full burden and largely succeeds: it enumerates action values, target as an address, workspace as number/name/'special:name', and then as desktop|screenshot|ui|none. The terse 'address' wording and the mention of a 'silent' flag not present in the schema keep it from a 5.

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?

States a specific verb+resource: window/workspace operations over IPC, and explicitly notes it is instant and vision-free, which nudges it apart from vision siblings like screenshot/click_ui. It does not name or contrast with siblings such as desktop or ui, so an agent still has to infer the boundary.

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 explicit when-not conditions: under HYPRUSE_BACKGROUND=1, workspace, focus_window and fullscreen are refused, and move_window is restricted to the agent's own workspaces. It lacks explicit guidance on choosing hypr over siblings like desktop or launch, but the conditional-use rules are solid.

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