Skip to main content
Glama

mouse_set

Assign a mouse trigger, such as wheel-up or gesture-left, to a player action, or pass "none" to disable it. Lets distinct mouse inputs share the same action.

Instructions

Point a mouse trigger at an action. Unlike keys, two triggers may share an action — wheel-up and drag-up both raising volume is fine, since the inputs are distinct. Pass "none" as the action to disable a trigger.

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": {
      "trigger": "<trigger>",
      "action": "<action>"
    },
    "name": "mouse_set"
  }
}

Input Schema

NameRequiredDescriptionDefault
actionYesAction id from keybind_list, or "none"
triggerYesTrigger id from mouse_list, e.g. wheel_up, gesture_left

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/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 a non-obvious constraint — multiple triggers may map to the same action because the inputs are distinct, unlike keys — plus the disable semantics. It says nothing about persistence, invalid-id handling, or what happens to an existing binding when reassigned.

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?

Three short sentences, front-loaded with the core action and followed by the one non-obvious rule and the disable path. No filler or restated field names beyond what the sentinel requires.

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 two-parameter setter with no output schema and no annotations, the description covers purpose, the disable path, and the key behavioral quirk. It stops short of error/return behavior, but little else is needed to call this correctly.

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%, so both parameters are already documented in the schema, including the "none" sentinel and example trigger ids. The description adds only the shared-action rule, which is a constraint rather than new parameter meaning, so baseline 3 applies.

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 opens with a concrete verb and resource: 'Point a mouse trigger at an action,' which is unambiguous about what gets mutated. It also draws a contrast with 'keys,' implicitly separating it from keybind_set, though it never names that sibling explicitly.

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?

It gives a clear use case (binding a mouse trigger to an action) and an explicit special-case instruction: pass "none" to disable a trigger. It does not state when to prefer mouse_reset over setting "none," nor any preconditions, so a small gap remains.

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