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

linux-computer-use-mcp

by dhakseshr

cursor_position

Retrieve the current mouse pointer location in screenshot coordinates, including the last server-moved position on Wayland, to target clicks, moves, and drags accurately.

Instructions

Where the pointer is, in screenshot coordinates (on Wayland: last position this server moved it to).

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

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?

No annotations are supplied, so the description carries the full burden. It does earn credit for a genuine behavioral caveat: on Wayland the value is only the last position this server set, not the true OS cursor, which materially changes how much an agent should trust the result. It does not state what happens if the pointer was never moved by the server, or whether the value can be stale on other platforms.

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?

One sentence, front-loaded with the core answer and the coordinate frame, with the platform caveat parenthetically attached. No filler and nothing to trim.

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?

This is a trivial zero-parameter read tool with an output schema, so the description need not explain return values. It covers the one non-obvious thing, the Wayland limitation, leaving only minor edge cases (unset pointer, error behavior) unstated.

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 tool takes no parameters, so there is nothing for the description to disambiguate; the baseline for a zero-parameter schema applies. The added note about coordinate frame is a bonus rather than a requirement.

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?

The phrase 'Where the pointer is, in screenshot coordinates' identifies a specific resource and the coordinate system it is expressed in, which is enough to tell it apart from siblings like move_mouse, click, and screenshot. It is framed as a noun phrase rather than an explicit verb, so it stops short of the crispest form, but the intent is unambiguous.

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?

There is no when-to-use guidance and no mention of alternatives. An agent must infer for itself that this is the read-side counterpart to move_mouse and that it exists to verify pointer position after a move or before a click.

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