Skip to main content
Glama
Sign In
Ghosthand

Ghosthand

by kumard3
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

scroll

Scroll the page vertically by a given pixel amount using human-like eased movements to bypass bot detection.

Instructions

Scroll the page by dy (and optional dx) pixels in eased human steps.

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": {
      "dy": "<dy>"
    },
    "name": "scroll"
  }
}

Input Schema

NameRequiredDescriptionDefault
dxNo
dyYes
stealthNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.9

TDQS

C2.9/5.0
Behavior2/5

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

The description mentions 'eased human steps' suggesting smooth scrolling, but fails to explain the effect of the 'stealth' parameter or behavior when scrolling exceeds page bounds. Without annotations, the description carries the full burden and is insufficient.

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 description is a single sentence with no superfluous words. Every part adds value, making it highly efficient for a simple tool.

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 basic scroll tool with three parameters and no output schema, the description is adequate but has gaps: it does not explain the 'stealth' parameter or boundary behavior. Sibling tools like drag or click might be alternatives, but no comparison is given.

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

Parameters2/5

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

Schema coverage is 0%, so the description should document parameters. It only partially explains dx and dy (pixels) but omits the 'stealth' parameter entirely. Units are implied but no details on sign conventions or limits.

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 clearly states that the tool scrolls the page by dy and optional dx pixels, with eased human steps. This distinguishes it from siblings like navigate (page navigation) or drag (scrolling by dragging). However, it does not explicitly mention that it scrolls within the current viewport.

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?

No guidance is provided on when to use scroll versus alternatives like drag or clicking on a scrollbar. The description does not mention any prerequisites or context for effective use.

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

Deploy Server

Other Tools