Skip to main content
Glama
Sign In
Computer Use MCP Server

Computer Use MCP Server

by SebastianBaltes
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

computer_left_click

Perform a left mouse click at precise screen coordinates. Hold a modifier key (shift, ctrl, alt, super) if needed.

Instructions

Click the left mouse button at the given coordinates. Optionally hold a modifier key (shift, ctrl, alt, super) during the click. The display is 1429x804 pixels (scaled from 1920x1080). All coordinates are in the scaled coordinate space.

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": {
      "x": "<x>",
      "y": "<y>"
    },
    "name": "computer_left_click"
  }
}

Input Schema

NameRequiredDescriptionDefault
xYesX coordinate
yYesY coordinate
modifierNoOptional modifier key to hold during click (shift, ctrl, alt, super)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.4/5.0
Behavior4/5

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

No annotations provided, so description fully carries burden. Discloses coordinate space scaling and display dimensions. Does not detail failure modes, but acceptable for a simple click.

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 sentences, each essential: action, modifier option, coordinate context. No redundancy or filler.

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?

No output schema; description does not mention return value. For a click action, success/failure could be mentioned, but the core functionality is well-covered. Fairly complete given simplicity.

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

Parameters4/5

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

Schema coverage is 100% (each param described). Description adds value by noting coordinates are in scaled space, which is not obvious from schema alone.

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?

Clearly states 'Click the left mouse button at given coordinates' and distinguishes from siblings like double_click, right_click. Includes optional modifier key, making purpose unambiguous.

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?

Provides clear context: coordinates, modifier key. Implicitly distinguishes from siblings (e.g., double_click for two clicks), but lacks explicit when-not-to-use.

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