Skip to main content
Glama
Sign In
mac-use-mcp

mac-use-mcp

by antbotlab
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

get_cursor_position

Read-only

Retrieve the current mouse cursor position in screen coordinates for macOS automation tasks.

Instructions

Get the current mouse cursor position in screen coordinates.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • src/tools/screen.ts:97-109 (handler)
    The implementation of the get_cursor_position tool handler, which calls the cursor input helper and returns the x and y coordinates.
    async function handleGetCursorPosition(): Promise<CallToolResult> {
  const response = await runInputHelper("cursor", {});
  const { x, y } = CursorPositionResponseSchema.parse(response);

  return {
    content: [
      {
        type: "text" as const,
        text: JSON.stringify({ x, y }),
      },
    ],
  };
}
  • src/tools/screen.ts:56-66 (registration)
    The registration of the get_cursor_position tool within the tool definitions list.
      {
    name: "get_cursor_position",
    description: "Get the current mouse cursor position in screen coordinates.",
    inputSchema: zodToToolInputSchema(GetCursorPositionInputSchema),
    annotations: {
      readOnlyHint: true,
      destructiveHint: false,
    },
  },
];

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.1

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, indicating a safe read operation. The description adds useful context by specifying 'screen coordinates' as the output format, which isn't covered by annotations. It doesn't mention rate limits or authentication needs, but this is acceptable given the tool's simplicity and annotation coverage.

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 a single, efficient sentence that front-loads the core purpose ('Get the current mouse cursor position') and adds essential detail ('in screen coordinates') without any wasted words. It's appropriately sized for a simple, parameter-less tool.

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 tool's low complexity (0 parameters, no output schema) and good annotations, the description is mostly complete. It clearly states what the tool does and the output format. A minor gap is the lack of explicit return value details (e.g., coordinate structure), but this is reasonable for such a straightforward tool.

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?

With 0 parameters and 100% schema description coverage, the baseline is 4. The description appropriately states there are no inputs needed ('Get the current...'), aligning with the empty schema and avoiding unnecessary parameter explanations.

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 specific action ('Get') and resource ('current mouse cursor position in screen coordinates'), distinguishing it from siblings like move_mouse, click, or get_screen_info by focusing solely on cursor position retrieval without any additional functionality.

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 for obtaining cursor coordinates, but provides no explicit guidance on when to use this tool versus alternatives like get_screen_info (which might include cursor data) or move_mouse (which involves cursor manipulation). It lacks clear when-not-to-use scenarios or prerequisites.

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