Skip to main content
Glama

keybind_reset

Restores a keyboard shortcut to its default setting, or resets every binding at once when no action is specified, undoing custom key mapping changes.

Instructions

Restore a shortcut to its default. Omit action to reset every binding at once.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "keybind_reset"
  }
}

Input Schema

NameRequiredDescriptionDefault
actionNoAction id. Omit to reset all.

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 behavioral burden. It usefully discloses the bulk-reset blast radius of omitting `action`, which is meaningful for a mutation tool. However, it does not state whether the reset is reversible, whether confirmation or special permissions are required, or what happens to bindings that have no default.

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 with zero filler. The primary operation is front-loaded, followed immediately by the important parameter behavior.

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 simple one-parameter reset tool with no output schema, the description covers the core action and the bulk-reset behavior. The main missing piece is the destructive/reversibility profile, which matters more here because no annotations are supplied.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and the schema already documents `action` as 'Action id. Omit to reset all.' The description restates the omit behavior in slightly different words but adds no new syntax, format, or validation detail. Baseline 3 is appropriate when the schema does the heavy lifting.

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?

The description gives a specific verb and resource: restore a shortcut to its default. This is clearly distinct from keybind_set (which changes a binding) even though it doesn't name siblings explicitly. The purpose is unambiguous and easy to match to a user intent.

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?

The definition explains the key usage variant: omit `action` to reset every binding at once. That is useful context for choosing between single and bulk reset, but it does not compare this tool to alternatives like keybind_set or keybind_list. Usage guidance is therefore implied rather than 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