Skip to main content
Glama
Sign In
mmjb-mcp

mmjb-mcp

by foklepoint
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

scroll

Move the current browser page down, up, to the top, or to the bottom to control page position during AI-driven browsing.

Instructions

Scroll the page; direction is down, up, top or bottom.

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

Input Schema

NameRequiredDescriptionDefault
directionNodown

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior2/5

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

With no annotations, the description carries the full burden of behavioral disclosure. It says nothing about whether the scroll is smooth or instant, how far one invocation scrolls, whether it targets the page or a focused element, or whether any state is returned — all relevant for an agent deciding how many times to call it.

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?

A single front-loaded sentence with no filler; the operation comes first and the argument domain second. Nothing could be trimmed without losing information.

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 one-optional-parameter tool with no output schema and no annotations, the description covers the basics (what it does, allowed directions) but omits scroll target, extent, and return behavior. Minimum viable rather than complete.

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 description coverage is 0% and the schema declares no enum, so the description's enumeration of 'down, up, top or bottom' is the only place the valid values appear and is genuinely load-bearing. It still doesn't explain the semantic difference between relative directions (down/up) and absolute ones (top/bottom).

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 and resource ('Scroll the page') and enumerates the valid directions, so an agent can tell it apart from the click/type/look/browse siblings without opening the schema. It stops short of explicitly naming a sibling or contrasting scope (element vs page), so it lands at clear-but-no-differentiation.

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 statement of when to use this tool versus the alternatives (e.g. goto for navigation, press for keyboard paging) and no prerequisites or exclusions. The only guidance is the direction vocabulary.

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