Skip to main content
Glama
Sign In
Computer Use MCP Server

Computer Use MCP Server

by SebastianBaltes
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

computer_mouse_move

Move the mouse cursor to specified screen coordinates without clicking. Coordinates use a scaled display of 1429x804 pixels.

Instructions

Move the mouse cursor to the given coordinates without clicking. 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_mouse_move"
  }
}

Input Schema

NameRequiredDescriptionDefault
xYesX coordinate
yYesY coordinate

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?

With no annotations, the description carries the full burden. It provides key behavioral context: the display size (1429x804 scaled from 1920x1080) and that coordinates are in scaled space. This clarifies the coordinate system and scaling, which is essential for correct usage.

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 sentences: the first states the purpose, the second provides critical coordinate context. No extraneous words. Every sentence earns its place, making it concise and front-loaded.

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 simple move tool with no output schema, the description covers the essential: what it does, the coordinate system, and that it doesn't click. It does not describe return behavior or error cases, but given the simplicity, this is acceptable.

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%, so baseline is 3. The description adds meaning by explaining that coordinates are in a scaled coordinate space and providing the display dimensions. This helps the agent understand the coordinate system, adding value beyond the bare schema descriptions.

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: 'Move the mouse cursor to the given coordinates without clicking.' It specifies the resource (mouse cursor) and the constraint (no clicking), effectively distinguishing it from clicking tools like left_click or right_click.

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?

The description explicitly mentions 'without clicking,' which signals that this tool should be used when a pure movement is needed, not a click. However, it does not explicitly state when not to use it or mention alternative tools for similar actions (e.g., click-and-drag).

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