Skip to main content
Glama
Sign In
SapperMCP

SapperMCP

by MasterX1582
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Click

click

Presses a mouse button at optional screen coordinates, moving the pointer first; supports left, middle, or right buttons for desktop automation.

Instructions

Click a mouse button, optionally at coordinates (moves first). button: left | middle | 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": "click"
  }
}

Input Schema

NameRequiredDescriptionDefault
xNo
yNo
buttonNoleft

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/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 does disclose that supplying coordinates moves the cursor before clicking, which is real behavior beyond the schema. It omits whether the click is dispatched to the OS, whether it blocks, and what happens to focus, which matters for a mutation-like input action.

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, front-loaded with the action and the coordinate condition, with the button values listed compactly. Nothing is padded or repeated.

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?

An output schema exists, so return values need not be explained. For an input-injection tool with no annotations, the description should still cover the coordinate reference frame and focus prerequisites; it covers the move-first side effect but not these.

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% and the schema defines button only as an unconstrained string, so the description's enumeration of left | middle | right adds genuine meaning. However, the x/y semantics are only called "coordinates" with no reference frame (screen vs window relative), units, or behavior on out-of-bounds values, leaving two of three parameters under-specified.

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 ("Click a mouse button") plus the scope of the coordinate option. It does not explicitly distinguish itself from the sibling double_click or drag_mouse, but the singular action is unambiguous enough to select on.

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 guidance on when to use this versus double_click, drag_mouse, or get_mouse_position, and no prerequisites such as whether the target window must be focused. The only conditional behavior mentioned is that coordinates trigger a move first.

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