Skip to main content
Glama
Sign In
Touchpoint

Touchpoint

by Touchpoint-Labs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

mouse_move

Move the mouse cursor to a specified UI element or screen coordinates. Use before scrolling to target a specific area.

Instructions

Move the mouse cursor to an element or to screen coordinates.

Use this before scroll() to scroll within a specific area.

Args:
    element_id: The element ID to move the cursor to.
    x: Screen X coordinate (use with y instead of element_id).
    y: Screen Y coordinate (use with x instead of element_id).

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

Input Schema

NameRequiredDescriptionDefault
element_idNo
xNo
yNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior3/5

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

No annotations provided, so description carries full burden. Describes two usage modes but does not mention whether move is instantaneous or has delays. Adequate but could be more transparent about async behavior.

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 efficient sentences plus clear 'Args' list. No redundant words. Front-loaded with main action.

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?

Covers main usage patterns and relationship with scroll(). Has output schema, so return not needed. Missing minor behavioral detail (e.g., if synchronous) but sufficient for a simple move action.

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 has no descriptions (0% coverage). Description explains element_id (element target) and x,y as coordinate alternative. Adds meaning beyond schema.

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?

Clear verb 'move' and resource 'mouse cursor', specifying two distinct modes (to an element or to screen coordinates). Distinguishes from siblings like 'click' and 'scroll'.

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?

Explicitly states to use before scroll() for specific area scrolling. Also clarifies parameter usage (element_id vs x,y). Lacks explicit when-not-to-use but adequate.

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