Shipvo

browser_scroll

Scroll the phone browser's page by dy CSS pixels (positive is down) and dx (positive is right). Returns the snapshot.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "session": "<session>"
    },
    "name": "browser_scroll"
  }
}

Input Schema

Name	Required	Description
`dx`	No
`dy`	No	Default 400
`session`	Yes	Session from open_app

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 7, 2026

TDQS

A3.5/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=false and destructiveHint=false, so the description does not need to restate safety. It adds useful behavior by specifying direction semantics and that the tool returns a snapshot, but it does not describe scroll bounds, page-state effects, or what the returned snapshot contains.

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?

The definition is one compact sentence with the action front-loaded and no redundant wording. Every element either states the operation or defines the axis semantics.

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?

For a simple three-parameter scroll tool with no output schema, the description covers the operation, axis semantics, units, and return behavior. It is somewhat incomplete on sibling selection and page-state effects, but it provides enough to invoke the tool correctly.

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 67%, and the description compensates by clarifying that dy and dx are in CSS pixels and by defining positive directions for both axes. It does not repeat the schema's session description, which is fine, though it leaves the dx default unstated.

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 states a specific verb and resource: scroll the phone browser's page by dx/dy pixels. It clearly distinguishes a browser-page scroll from a generic screen scroll through the resource wording, but it does not explicitly name the sibling scroll tool or contrast the two.

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?

The description explains axis direction but gives no guidance on when to use browser_scroll versus siblings such as scroll, browser_click, or browser_snapshot. There are no prerequisites, alternatives, or when-not-to-use conditions.

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

All Shipvo tools Inspect

Try in Browser

Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.