Skip to main content
Glama
Sign In
Computer Use MCP Server

Computer Use MCP Server

by SebastianBaltes
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

computer_middle_click

Middle-click at specified coordinates on a Linux X11 desktop to automate actions like opening links in new tabs or pasting clipboard selection.

Instructions

Middle-click at the given coordinates. 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_middle_click"
  }
}

Input Schema

NameRequiredDescriptionDefault
xYesX coordinate
yYesY coordinate

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4/5.0
Behavior3/5

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

No annotations are provided, so the description carries full burden. It discloses the coordinate scaling and display size, but lacks details on the effect of middle-click (e.g., opening links, closing tabs) 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 two concise sentences, front-loading the action and immediately providing critical coordinate scaling information. No unnecessary words.

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?

Given the simplicity of the tool (2 parameters, no output schema), the description is largely complete. It explains the coordinate system but could mention the typical effect of middle-click to fully inform agent behavior.

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?

The input schema describes x and y as coordinates. The description adds meaning by specifying that all coordinates are in a scaled coordinate space (1429x804 from 1920x1080), which is crucial for correct positioning.

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 'Middle-click' and the resource 'at the given coordinates'. It distinguishes from sibling tools like left_click, right_click, and double_click by specifying the middle-click behavior.

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?

The description implies usage through the name and action but does not explicitly state when to use middle-click versus other click types, nor does it mention prerequisites or exclusions.

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