Skip to main content
Glama
RapidMiner / Altair AI Studio MCP

RapidMiner / Altair AI Studio MCP

rm_scroll

Scrolls the mouse wheel over a specified UI component or screen point to move content, with positive amounts scrolling down and negative amounts scrolling up.

Instructions

Mouse-wheel scroll over a component or point. amount>0 scrolls down, <0 up.

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

Input Schema

NameRequiredDescriptionDefault
xNoX in window coordinates (pixels of an unscaled rm_screenshot)
yNoY in window coordinates
idNoComponent id from rm_ui_tree / rm_ui_find
nameNoMatch Swing component name
textNoMatch visible text / label (substring, case-insensitive)
classNoMatch Java class name, e.g. JButton, JTree
exactNoExact (not substring) text match
indexNoWhich match to use when several match (0-based)
scaleNoIf x/y come from a scaled screenshot, pass that scale
amountNo
windowNoWindow id from rm_windows (default: active window)
tooltipNoMatch tooltip text
modifiersNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full disclosure burden. It explains scroll direction but not the unit of amount (wheel notches? pixels?), whether the target window must be focused or is activated automatically, whether the call blocks, or what happens when several components match.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two clipped sentences, direction semantics front-loaded after the action, with no filler. The '>'/'<' shorthand is compact and readable, though slightly terse for a 13-parameter tool.

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?

For a 13-parameter input-simulation tool with zero annotations and no output schema, the definition is thin. An agent must infer targeting precedence, scroll magnitude, focus requirements and multi-match resolution entirely from the schema descriptions.

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 85%, so the schema documents most parameters already. The description does add value for the one gap: 'amount' has no schema description, and the sign convention (>0 down, <0 up) is explained here. It adds nothing about modifiers, index or scale behavior beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and mechanism (mouse-wheel scroll) plus the target (component or point), which is enough to tell it apart from rm_click, rm_drag and rm_key. It stops short of explicitly naming an alternative, but the action is unambiguous.

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

Usage Guidelines2/5

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

There is no when-to-use guidance versus siblings, and no advice on choosing between the component-targeting path (id/name/text/class) and the coordinate path (x/y). The phrase 'over a component or point' implies two modes but leaves the selection entirely to inference.

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