Skip to main content
Glama

macos_mouse_current_position

Read the current macOS mouse cursor position in logical points without moving it, so you can verify a prior cursor move landed correctly before clicking or dragging.

Instructions

macOS only. Read the mouse cursor's current absolute position in logical coordinates (macOS points, top-left origin) without moving it. Use this to confirm a prior macos_mouse_move landed where expected before clicking or dragging. Requires Accessibility permission because it reuses the shared input session.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.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 and does well: it discloses that the tool is non-mutating, that it requires Accessibility permission, and why (shared input session reuse). It stops short of stating what happens when the permission is not granted or how coordinates behave across multiple displays.

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 short sentences, front-loaded with the platform constraint and the operation itself, followed by intended use and the permission requirement. No redundant or filler wording.

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 zero-parameter read tool with no output schema, the description supplies the coordinate frame and units needed to interpret the result. The remaining gap is the shape of the returned value (e.g., how x/y are exposed), which an agent would have to discover from the response.

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 zero parameters, so there is nothing for the description to disambiguate. Baseline of 4 applies; the coordinate-system sentence is useful context rather than parameter guidance.

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?

Names a specific verb and resource: read the mouse cursor's current absolute position. It also specifies the coordinate semantics (logical points, top-left origin) and the non-effect ('without moving it'), which separates it cleanly from macos_mouse_move and the click/drag siblings.

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?

Gives a concrete use case: verifying that a prior macos_mouse_move landed where expected before clicking or dragging, which implicitly tells the agent not to use it for movement. It does not spell out when this check is unnecessary or what to do if the reading disagrees with the expectation.

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