Skip to main content
Glama

mouse_click

Clicks a left or right mouse button in the active window, with an optional hold duration, so AI agents can perform mouse actions in games and mouse-controlled apps.

Instructions

Click the mouse ('left' or 'right').

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_click"
  }
}

Input Schema

NameRequiredDescriptionDefault
buttonNoleft
hold_msNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.2

TDQS

C2.7/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 and falls well short. It does not say whether the click occurs at the current cursor position, what hold_ms actually does (press-and-hold duration), whether the action is reversible, or what the tool returns; for an input-injection tool that can trigger arbitrary UI actions, that is a meaningful gap.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

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

A single short sentence that is front-loaded with the core action and free of filler. Its brevity becomes under-specification rather than a structural flaw, but nothing is wasted or buried.

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

Completeness2/5

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

With no annotations and no output schema, this definition is the agent's only source of behavioral detail, and it omits cursor-position assumptions, the hold_ms semantics, and any result information. For a two-parameter input-injection tool, that leaves it materially incomplete.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must compensate and does not. It documents the button values (left/right), which the schema itself leaves enum-less, but says nothing about hold_ms — a non-obvious timing parameter with a default of 80 — leaving half the parameters undefined in both places.

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 states a specific verb and resource — 'Click the mouse' — with the button variants enumerated. It is clear what the tool does, but it draws no boundary against nearby siblings such as mouse_move or press, so the agent gets no help distinguishing it from those.

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

Usage Guidelines2/5

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

There is no when-to-use guidance, no mention of prerequisites (e.g., that the pointer must already be positioned), and no reference to alternatives like mouse_move or combo. The agent must infer the workflow context entirely on its own.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.