Skip to main content
Glama

ie_scroll

Scroll pages, containers, or elements into view by selector/value, to top or bottom, or by pixel offsets—useful for virtualized grids.

Instructions

Scroll: bring an element into view (by/value), scroll page/container to top|bottom (to=...), or by pixels (dx/dy). Needed for virtualized grids.

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

Input Schema

NameRequiredDescriptionDefault
byNo
dxNo
dyNo
toNotop | bottom
frameNo
valueNo
targetNoWhere to act: omit it for the session's IE driver; hwnd:<n> acts over COM on the window <n> (a modal dialog's hwnd from a NOTICE or ie_windows), tab:<n> on an attached tab. Over COM, DOM access is script, input is synthetic (script events and a timer click, not mouse or keyboard input; keys are posted window messages) and only id, name, tag, class, link_text and (documentMode 8+) css locators work.
timeoutNoseconds to wait for the element (default 10)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

B3.1/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. Beyond naming scroll modes and mentioning virtualized grids, it says nothing about return values, wait/error behavior, whether scrolling is immediate or animated, or side effects on the viewport; the schema's target description covers COM behavior, but the description itself adds little behavioral context.

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?

It is a single compact sentence that front-loads the verb and groups the three scrolling modes efficiently. The parenthetical syntax is terse but not wasteful, though it is slightly cryptic for a reader unfamiliar with the parameter names.

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 eight parameters, no annotations, and no output schema, the definition needs more context than a one-line mode summary. Frame, timeout, and return/error behavior are not covered by the description, and target details live only in the schema; the virtualized-grid note is valuable, but the overall definition is thin for this complexity.

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 only 38%, so the description must compensate. It usefully maps by/value to element scrolling, to to page/container top|bottom, and dx/dy to pixel scrolling, but it leaves the frame parameter unexplained and does not define accepted by locator types, so compensation is only partial.

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?

The first clause uses a specific verb, 'Scroll', and enumerates three distinct modes: element into view via by/value, page/container to top|bottom via to, and pixel movement via dx/dy. It is clearly about scrolling, but it does not name or contrast a sibling such as ie_grid, so it falls short of full sibling differentiation.

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?

The phrase 'Needed for virtualized grids' supplies a concrete use case, so usage guidance is not entirely absent. However, it gives no explicit when-not guidance, no alternatives, and no prerequisites for choosing element scrolling versus page/container scrolling versus pixel scrolling.

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