Skip to main content
Glama
Sign In
Body-MCP

Body-MCP

by sspublisher2005-gif
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

hands_scroll

Scroll the browser page up or down by a set amount (1-50) to move an agent's view to the needed content.

Instructions

Scroll the browser page. direction: up|down. amount: 1-50.

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

Input Schema

NameRequiredDescriptionDefault
amountNo
directionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden, and it discloses very little. It does not say whether the call waits for scrolling to settle, whether it errors when no page is attached, or whether it returns the new scroll position.

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 action statement followed by terse parameter hints, with zero filler. It is arguably too compressed rather than padded, losing only minor efficiency for missing detail.

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

Completeness2/5

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

For a simple two-parameter tool this is close to adequate, but with no annotations, no output schema, and 0% schema coverage, the description should say what a unit of amount means and what the caller can expect afterward. Those omissions leave the agent guessing at the only non-obvious parameter.

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 0% and the schema has no enum, so the description is the only thing that defines direction as up|down and bounds amount to 1-50 — real added value. However, the unit of amount (pixels, lines, notches) remains undefined, so it only partially compensates.

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?

States a specific verb+resource ("Scroll the browser page"), which is plainly distinct from the click/press/type siblings. It does not explicitly name a sibling to distinguish itself from, but the action is unambiguous.

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 on when to use this versus hands_press (e.g. PageDown) or hands_open, and no prerequisites such as a browser needing to be attached first. The agent must infer that this is for moving viewport content off-screen.

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