Skip to main content
Glama
IlyasKhallouki

hypruse

by IlyasKhallouki
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

use_bind

Destructive

Run a configured Hyprland keybind by its combo to execute the bound action directly; synthetic keypresses cannot trigger compositor binds, so use this for launchers or layout shortcuts.

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 or the background guarantee is on (HYPRUSE_BACKGROUND=1): a bind runs an arbitrary compositor action that cannot be scoped to a window.

Input Schema

NameRequiredDescriptionDefault
thenNonone
comboYes

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

TDQS

A4.9/5.0
Behavior5/5

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

Annotations already mark it destructive/non-readOnly, but the description adds substantial behavior beyond them: the refusal conditions tied to environment variables, the justification that it executes an arbitrary compositor action that cannot be scoped to a window, and how the `then` result is appended to the call.

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?

Front-loaded with purpose and example, then rationale, use cases, the secondary parameter, and finally refusal conditions. Every sentence adds distinct information with no filler.

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?

Given an output schema exists, return values needn't be described. The description covers purpose, params, refusals, and safety posture fully; an agent has everything needed to invoke it correctly or know it will be rejected.

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%, so the description must carry the load and largely does: `combo` is explained as a combo string sourced from the `binds` tool with an example, and `then` is enumerated ('desktop'|'screenshot'|'ui'|'none') with its append behavior. It stops short of documenting the default ('none') or exact combo syntax rules.

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?

Specific verb+resource: 'Run one of the user's own Hyprland keybinds by its combo', with a concrete example ('SUPER+F'). It explicitly distinguishes itself from synthetic-key approaches and points to the sibling `binds` tool as the source of valid combos.

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?

States when to use it ('to drive the owner's configured workflows: launchers, layout shortcuts, scratchpads') and when it is refused (HYPRUSE_CONFINE set, HYPRUSE_BACKGROUND=1), plus the rationale that synthetic keypresses cannot trigger compositor binds. Both the use case and the exclusion conditions are explicit.

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