Skip to main content
Glama

Scroll the page

cotlet_browser_scroll
Read-onlyIdempotent

Scrolls with the mouse wheel: down or up by screens, to top or bottom, until element is in view, or inside a panel or list (inside). Content that loads on scroll appears. Answers the page after it: the elements and text in view, with the same numbers.

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

Input Schema

NameRequiredDescriptionDefault
appNoLeave it out: the step runs in the user's web browser. Only when cotlet_app_guide names an app's own Cloud Browser, that app's slug, e.g. milanote.
tabNoThe Tab id of the last answer. The step acts only while that tab is the shown one; if the user or another client showed another tab, it does nothing and answers tab_changed. Leave it out to act on the shown tab.
insideNoScroll inside this element, not the page.
elementNoScroll until this element is in view.
screensNoViewport heights, for down and up. Default: 0.8.
directionNoDefault: down.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / tab
      Added value: +{
      +  "description": "The Tab id of the last answer. The step acts only while that tab is the shown one; if the user or another client showed another tab, it does nothing and answers tab_changed. Leave it out to act on the shown tab.",
      +  "maxLength": 64,
      +  "minLength": 1,
      +  "type": "string"
      +}
  2. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already cover safety (readOnly, idempotent, non-destructive) and open-world scope, so the description's marginal value is what it adds on top: the fact that scrolling can trigger content loading, and that the call returns the page state afterwards. It could still say more about limits (maximum scroll distance, behaviour when the element is absent), but the lazy-load disclosure is genuinely useful 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?

Two tight sentences, front-loaded with the verb and mode enumeration, then the return behaviour. Slightly telegraphic phrasing such as 'with the same numbers' relies on numbering conventions established elsewhere, which costs a little clarity for a first-time reader.

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 stating that the call answers with the elements and text in view. For a 6-parameter, zero-required tool that is mostly complete; only failure modes (element never found, scroll limit reached) are unaddressed.

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

Parameters4/5

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

Schema coverage is 100%, so a 3 would be the floor, but the description goes beyond the schema by explaining how the parameters interact: `screens` applies to down/up, `element` selects the scroll-until-visible mode, and `inside` changes the scroll target from page to panel. That relational mapping is not expressed in the individual property descriptions.

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 description gives a concrete verb ('Scrolls with the mouse wheel') and then enumerates every supported mode — down/up by screens, to top/bottom, until an element is in view, or inside a panel. That is far more specific than the title. It stops short of naming siblings such as cotlet_browser_read or cotlet_browser_find, so the boundary against a plain page read is left for the agent to infer.

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?

Usage is implied through the mode list: scroll when you need lazy-loaded content ('Content that loads on scroll appears') or when a target is off-screen. There is no explicit when-not guidance, no alternatives named, and no statement of what to do if the target element never comes into view.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources