OmniCommanderMCP

by kaannsaydamm

Overview Schema Source Related Servers Discussions Admin

TypeScript

Local

mouse_click

Perform left, middle, or right mouse button clicks at optional (x, y) screen coordinates.

Instructions

Click left, middle, or right mouse button, optionally at coordinates.

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

Name	Required	Default
`x`	No
`y`	No
`button`	No	left

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jul 10, 2026

TDQS

B3.2/5.0

Behavior2/5

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

The description does not specify whether the mouse is moved to coordinates before clicking if x/y are provided, or what the default behavior is when coordinates are omitted. No details on click type (single, double) or any side effects.

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?

The description is a single sentence that conveys the core purpose efficiently without extraneous words.

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 simple mouse click tool, the description covers the basic functionality. However, it lacks usage context and fails to specify key behavioral details that an agent would need to invoke it correctly.

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?

The description only mentions 'coordinates' and 'button' but does not explain the coordinate system (e.g., screen vs. window), the meaning of the numeric values, or the button default when not specified.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action (click), the button options (left, middle, right), and optional coordinates. It distinguishes from sibling tools like mouse_move, which only moves the cursor, and keyboard_type.

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?

The description provides no guidance on when to use this tool versus alternatives such as mouse_move or keyboard shortcuts. There is no mention of prerequisites or typical use cases.

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