Skip to main content
Glama
IlyasKhallouki

hypruse

by IlyasKhallouki
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

use_bind

Trigger a saved Hyprland keybind by its combo (e.g. SUPER+F) to run the owner's configured launcher, layout shortcut, or scratchpad when synthetic keypresses cannot activate compositor binds.

Instructions

Run one of the user's own Hyprland keybinds by its combo (from the binds tool), e.g. 'SUPER+F'. This executes the bound action directly (the only reliable way: synthetic keypresses do not trigger compositor binds). Use it to drive the owner's configured workflows: launchers, layout shortcuts, scratchpads. then ('desktop'|'screenshot'|'ui'|'none') appends the result to this call (handy after a launcher bind). Refused while HYPRUSE_CONFINE is set: a bind runs an arbitrary compositor action that cannot be scoped to a window.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
thenNonone
comboYes

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. Addedv0.2.1

TDQS

A4.5/5.0
Behavior4/5

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

With no annotations provided, the description carries the full burden. It discloses that the tool executes an arbitrary compositor action, that it is refused under HYPRUSE_CONFINE, and that synthetic keypresses do not trigger compositor binds. It does not detail side effects or reversibility, but for a tool that runs user-defined binds, the key behavioral constraints are clearly stated.

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 compact and front-loaded with the core action and example. Every sentence adds value: the reliability rationale, use cases, 'then' semantics, and the confinement refusal. It is slightly dense, but not bloated.

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 complexity (running arbitrary user keybinds) and the absence of annotations, the description covers the essential context: what it does, why it's needed, when it's refused, and how 'then' works. It doesn't describe the output schema, but an output schema exists, so that burden is partially lifted. Minor gaps remain around error behavior if the combo is invalid.

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%, so the description must compensate. It explains 'combo' with an example and clarifies that it comes from the 'binds' tool. It also explains the 'then' parameter's purpose and its allowed values ('desktop'|'screenshot'|'ui'|'none'). This is strong compensation, though it could be slightly more explicit about the exact format of 'then' values.

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 states a specific verb ('Run'), a specific resource ('one of the user's own Hyprland keybinds by its combo'), and gives a concrete example ('SUPER+F'). It also distinguishes itself from synthetic keypresses and from the sibling 'binds' tool, making its purpose unmistakable.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explicitly says when to use it ('to drive the owner's configured workflows: launchers, layout shortcuts, scratchpads') and when not to use it ('Refused while HYPRUSE_CONFINE is set'). It also explains why it is the only reliable way, which helps an agent choose it over alternatives like synthetic keypresses or the 'binds' tool.

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