Skip to main content
Glama

Glasswarp

by com.glasswarp

input.drag

Destructive

Press-move-release mouse drag in native capture coordinates. Use for drawing, sliders, selection boxes, and drag-and-drop. Side effect: mouse_down → moves → mouse_up on the remote desktop. Prefer input.send_actions if the drag is one step in a longer predictable sequence.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
to_xYesNative end X
to_yYesNative end Y
from_xYesNative start X
from_yYesNative start Y
session_idYesActive session id
duration_msNoApprox drag duration in ms; more steps when larger (default ~200)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
okYesFalse when the tool failed
messageYesHuman-readable result for the agent

TDQS

A4.6/5.0
Behavior5/5

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

Discloses side effect of mouse_down → moves → mouse_up, and annotations include destructiveHint=true; no contradiction, and adds value beyond annotations.

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 sentences with zero fluff; purpose, use cases, side effect, and alternative are all front-loaded.

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 purpose, usage, side effect, and alternative; output schema exists so return values need not be described. Could mention coordinate units but not necessary given schema bounds.

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

Parameters3/5

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

Schema coverage is 100%, so baseline 3; description adds no extra meaning beyond schema descriptions, which already adequately define each parameter.

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?

Description clearly states 'Press-move-release mouse drag' as specific verb+resource, lists use cases (drawing, sliders, etc.), and distinguishes from input.send_actions.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly says when to use (drawing, sliders, selection boxes, drag-and-drop) and when to prefer alternative (input.send_actions for longer sequences).

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

All Glasswarp toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.6/5.0
Disambiguation5/5

Each tool has a clearly distinct purpose: session management, input methods, screen observation, demo retrieval, and rig listing. Descriptions explicitly state when to prefer one over another (e.g., click_target over click_xy, send_actions over chaining). No two tools overlap in functionality.

Naming Consistency5/5

All tools follow the domain.verb_noun pattern (e.g., app.launch, input.click_target, session.start) with consistent snake_case. Verbs like launch, list, get, click, send, type, observe are clear actions, and the naming is predictable across the entire set.

Tool Count5/5

16 tools cover the full spectrum of remote desktop control: 2 for demos, 1 for rigs, 4 for sessions, 1 for screen, 7 for input, and 1 for app launching. Each tool is necessary and there is no redundancy; the count is well-scoped for the domain.

Completeness5/5

The tool set provides a complete lifecycle for remote desktop interaction: rig selection, session start/end, screen observation, all common input actions (click, type, scroll, drag, multi-step sequences), app launching, and demo retrieval. There are no obvious gaps for typical UI automation tasks.

Resources