Skip to main content
Glama
mcp-cui-chrome

mcp-cui-chrome

by cuipy

滚动

browser_scroll

Scroll the current Chrome page up or down by a set number of pixels, showing direction before and success status after each segment.

Instructions

通用:在当前页面分段滚动。开始前显示方向,结束后显示是否成功。

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": {
      "direction": "<direction>"
    },
    "name": "browser_scroll"
  }
}

Input Schema

NameRequiredDescriptionDefault
pixelsNo滚动像素,默认大约 480 到 760
directionYes滚动方向

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.0.4

TDQS

B3.4/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden of disclosure. It does disclose real behavior: scrolling happens in segments, the direction is surfaced before the action, and success is reported afterward. It does not say whether the scroll is animated, whether page state or a new snapshot is returned, or whether the 4000px cap is enforced by clamping or by error, so meaningful gaps remain.

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 with no padding, and the core action is front-loaded after the "通用" qualifier. It is slightly under-specified rather than verbose, but structurally clean.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a two-parameter action tool with no output schema and no annotations, the definition covers the action and a hint of the result (success flag), but it leaves the return shape and post-scroll page state unstated. It is adequate but not complete.

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 description coverage is 100%, with both the `direction` enum and the `pixels` range already documented in the schema. The description adds only the notion of segmented scrolling and of direction being shown, which does not extend the parameters' meaning beyond the schema. Baseline 3 is appropriate.

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 specific verb and resource: "在当前页面分段滚动" (scroll the current page in segments). That is clear enough to distinguish this tool from the non-scrolling siblings such as browser_click and browser_snapshot. It does not compare itself with any alternative, but no sibling competes with it, so this is a minor gap.

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 word "通用" signals general-purpose applicability, and "分段滚动" implies incremental scrolling, which is typical for revealing lazy-loaded content. However, the description never states when an agent should scroll instead of using browser_snapshot or browser_navigate, nor does it mention prerequisites or exclusions. Usage is only implied.

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