Skip to main content
Glama

owa_scroll

Scroll a windowed list to reveal off-screen rows, then report its position, bottom state, and labels available to press. Use it when a row past the fold cannot be found until the list moves.

Instructions

Scroll a list in the app to reach rows that are not on screen -- the long lists are windowed, so a row past the fold matches nothing until the list is scrolled. find names the list, its panel or a row in it (default: the biggest list on screen); to is down (default), up, top or bottom. Answers where the list is now, isAtBottom, and inView: the labels that can be pressed after the scroll.

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

Input Schema

NameRequiredDescriptionDefault
toNo
findNoThe list, panel or a row in it, by label
pageNoPart of the window URL, e.g. "reader.html"; default the main window.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2026.11.15

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses the windowing behavior that motivates the tool, the defaults for both optional parameters, and what the result reports (current position, isAtBottom, inView). It does not mention that scrolling mutates UI state or any failure modes, which keeps it below a 5.

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?

Front-loaded with the purpose and rationale, then parameter semantics, then return values — a logical order with no filler. The single dense sentence with inline backticked tokens is slightly heavy but every clause earns its place.

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?

No output schema exists, and the description compensates by naming the returned fields (position, isAtBottom, inView). Defaults for all optional parameters are covered; only the `page` parameter's role is left implicit, which is a minor gap for a 3-parameter tool.

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 67%, and the description adds real meaning for `find` (list, panel, or a row within it; defaults to the biggest list on screen) and `to` (down default, plus up/top/bottom). The `page` parameter is left entirely to the schema, so the description only partially compensates for the coverage gap.

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?

States a specific verb and resource ("Scroll a list in the app") and immediately explains the reason (windowed lists mean off-screen rows match nothing). An agent can distinguish this from owa_click or owa_find_ui without opening any schema.

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

Usage Guidelines4/5

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

Gives a clear condition for use: rows past the fold match nothing until the list is scrolled, which tells the agent when scrolling is required. It does not name an alternative tool or state when not to use it, so it stops short of full routing guidance.

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