Skip to main content
Glama

Glasswarp

by com.glasswarp

input.scroll

Destructive

Move the cursor to native (x,y) then apply a vertical mouse-wheel delta. Side effect: scroll on whatever is under that point. Negative delta scrolls toward the bottom of the page. Prefer input.send_actions when scroll is part of a multi-step sequence. Re-observe after scrolling lists/pages before clicking targets.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
xYesNative X to hover before scrolling
yYesNative Y to hover before scrolling
deltaYesVertical wheel delta (negative = toward bottom of page)
session_idYesActive session id

Output Schema

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

TDQS

A4.5/5.0
Behavior4/5

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

Discloses side effect (scroll on element under point) and delta direction, adding context beyond annotations that already indicate destructive nature; could mention coordinate bounds but not critical.

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 sentences front-loading core action, then side effect, then guidance—no filler, every sentence informative.

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

Completeness5/5

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

Complete for a scroll tool with clear parameters and output schema; covers side effect, alternative tool, and post-action advice.

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 descriptions already fully cover all 4 parameters; the description only restates delta sign meaning, adding minimal incremental value beyond the 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?

Clearly states action: move cursor then apply vertical mouse-wheel delta, with side effect on element under point. Distinguishes from sibling tools like input.click_xy, input.drag by specifying scroll and delta direction.

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 advises preferring input.send_actions for multi-step sequences and recommends re-observing after scrolling before clicking, providing clear when-to-use and when-not-to guidance.

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