Skip to main content
Glama

mouse_reset

Restore a mouse trigger to its default, or omit the trigger to reset all mouse triggers at once. Use it when mouse controls need a known baseline.

Instructions

Restore a mouse trigger to its default. Omit trigger to reset all of them.

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": "mouse_reset"
  }
}

Input Schema

NameRequiredDescriptionDefault
triggerNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full burden. It does disclose the bulk behavior of resetting everything when the parameter is omitted, but says nothing about whether resets are reversible, what the defaults are, whether permissions are required, or how invalid triggers are handled 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 with zero filler, and the primary action is front-loaded before the optional-parameter behavior. Nothing could be removed without losing information.

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 one-parameter tool with no output schema the description covers the core action and the omit-to-reset-all case, but leaves the trigger value domain and error/edge-case behavior undefined. Adequate but with clear gaps given the absence of annotations and schema descriptions.

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 0%, so the schema alone only shows an optional string. The description adds real meaning by explaining that omitting the parameter resets all triggers, but it never states what values `trigger` accepts or how a trigger is identified, so the single parameter remains partially opaque.

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?

States a specific verb and resource: 'Restore a mouse trigger to its default.' An agent can distinguish this from mouse_set and mouse_list by the reset semantics, though the term 'mouse trigger' is never defined, leaving mild ambiguity about what entity is being reset.

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 description gives clear scope guidance via 'Omit `trigger` to reset all of them,' which tells the agent how to use the parameter but not when to prefer this tool over mouse_set or other reset siblings. Usage is implied rather than stated with alternatives.

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