Skip to main content
Glama

keybind_set

Rebind an Unflick keyboard shortcut to a chosen action and key. Detect conflicts when a key is already assigned, naming the conflicting action instead of overwriting it.

Instructions

Rebind a keyboard shortcut. Fails if the key is already taken by another action, naming the conflict rather than silently stealing it.

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>",
      "key": "<key>"
    },
    "name": "keybind_set"
  }
}

Input Schema

NameRequiredDescriptionDefault
keyYesKey, e.g. k · Shift+z · Mod+o · PageUp
actionYesAction id from keybind_list, e.g. play_pause

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose one important trait: the call fails on a key conflict and reports the conflicting action instead of overwriting silently. It does not say whether the action's previous key is replaced, whether the change persists, or what the response looks like, which leaves meaningful gaps 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short sentences, both of which earn their place: the first states the action, the second states the failure contract. Front-loaded with no filler.

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

Completeness3/5

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

For a two-parameter tool with a fully documented schema, the description covers purpose and conflict behavior adequately. It nonetheless omits the overwrite/replace semantics and any indication of what a successful call returns, which matter for a rebinding mutation with no annotations or output schema.

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 100% and both parameters carry inline examples ("k · Shift+z · Mod+o · PageUp" and "play_pause"), so the schema already does the work. The description adds no extra parameter meaning, but it correctly points at keybind_list as the source of valid action ids, which is a small useful connection.

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?

"Rebind a keyboard shortcut" gives a specific verb (rebind) and resource (keyboard shortcut), which clearly separates it from keybind_list and keybind_reset. It stops short of naming those siblings in the description, but the intent is unambiguous.

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

Usage Guidelines3/5

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

Usage is only implied by the purpose: an agent can infer you call this to change an existing binding. There is no explicit guidance on when to prefer this over keybind_reset, nor any statement of prerequisites, so routing must be guessed from the sibling names.

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