Skip to main content
Glama
linux-computer-use-mcp

linux-computer-use-mcp

by dhakseshr

click

Move the pointer to specified screen coordinates and press a mouse button, optionally with modifiers or multiple presses, then capture a screenshot to confirm the screen state.

Instructions

Glide the pointer to x,y and click. Returns a screenshot once the screen settles.

clicks: 1 = single, 2 = double, 3 = triple click. modifiers: keys held during the click, e.g. ["ctrl"] or ["shift"]. screenshot: set false to skip the follow-up screenshot (e.g. mid-sequence).

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

Input Schema

NameRequiredDescriptionDefault
xYes
yYes
buttonNoleft
clicksNo
modifiersNo
screenshotNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

A3.5/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 burden and does disclose meaningful behavior: it waits for the screen to settle and returns a screenshot, which an agent needs to know for sequencing. It does not disclose whether coordinates are screen- or window-relative, whether an out-of-bounds coordinate fails, or what happens if the target window lacks focus.

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?

The action and return value are front-loaded in one sentence, then the remaining lines are compact per-parameter notes with no filler. Slightly more compact than prose without losing any needed detail.

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?

For a 6-parameter UI automation tool with no annotations and no output schema, the definition covers the action, the return value, and the non-obvious parameters. The notable remaining gap is coordinate semantics (screen vs. window relative), which matters for correct invocation but is a single omission rather than a systemic shortfall.

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 description coverage is 0% across 6 parameters, so the description must compensate. It explains clicks (1/2/3), modifiers (keys held during the click, with examples), and screenshot, but leaves button unmentioned despite having a default and enum, and never clarifies the coordinate space for x/y.

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?

"Glide the pointer to x,y and click" states a concrete verb (click) and resource (pointer at coordinates), and the follow-up sentence clarifies the return value. It implies a combined move+click action that differs from move_mouse, but never names that sibling explicitly, so disambiguation is inferred rather than stated.

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?

Usage context is only implied through parameter guidance: "screenshot: set false to skip the follow-up screenshot (e.g. mid-sequence)" is a real piece of workflow advice. There is no statement of when to prefer this over move_mouse, drag, or press_key, and no preconditions or exclusions.

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