Skip to main content
Glama

pointer_drag

Drag from one point to another with real intermediate motion, avoiding press-and-teleport. Specify start and end coordinates and optionally dwell before release for reliable drops.

Instructions

Press at one point, travel, release at another. The travel is real intermediate motion, because a press-and-teleport is not a drag to most toolkits.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
lookNoWhat to show you afterwards. Default "auto": wait for the screen to stop changing, measure how much this action changed, and attach a picture of the affected window only if something did change -- so a click that hit nothing costs no tokens and says so. "window" always attaches it, "screen" uses the whole desktop (slower, 6x the tokens), "region" uses look_at, false skips all of it. Use false for the middle of a sequence you are going to check at the end anyway.auto
to_xYes
to_yYes
stepsNo
buttonNoleft
from_xYes
from_yYes
look_atNoRectangle for look:"region", in screen pixels. Object form {x, y, width, height} or array form [x, y, width, height].
dwell_msNoHover at the destination this long before releasing. Default 0 is the timing measured at 5/5 on a real drop target; a slower variant scored 4/5, so this is NOT a better default. Try ~400 only after a cross-app drop has actually failed (GTK source, Electron target).
settle_max_sNoHow long to wait for the screen to stop changing before looking. Raise it for an app that animates slowly; set it to 0 to capture immediately.
expect_windowNo
Install Server

TDQS

A3.5/5.0
Behavior3/5

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

No annotations are present, so the description must shoulder the behavioral burden. It does disclose the crucial non-obvious trait that the travel is real intermediate motion, not a teleport. However, it omits other meaningful behaviors such as the default left button, step count, and how look/settle affect results.

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 tight sentences, front-loaded with the action and then a discriminating behavioral caveat. No wasted words.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With 11 parameters, no annotations, and no output schema, the description is too thin to be complete. It covers the drag concept but not the parameter landscape, expected outcomes, or failure modes.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is only 36%, so the description needs to compensate for undocumented parameters like steps, button, and expect_window. It only loosely covers from/to coordinates and says nothing about the other parameters, leaving the agent undersupplied.

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 defines the action: press at one point, travel, release at another. It is specific about being a real drag with intermediate motion, distinguishing it from pointer_move and similar siblings.

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?

Implied usage is clear – use for actual drag gestures where toolkits need real motion. But it does not explicitly name alternatives or state when not to use it, leaving the routing partly to inference.

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

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/tristanmuzzu/deskwright'

If you have feedback or need assistance with the MCP directory API, please join our Discord server