Skip to main content
Glama
rahulkr
by rahulkr

scroll_up

Scroll up on Android device screens to navigate content or test UI interactions. Use this ADB tool for development, testing, and debugging workflows.

Instructions

Scroll up on the current screen

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
device_serialNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The main handler function for the 'scroll_up' tool. It calculates the screen dimensions, determines the swipe coordinates from 30% to 70% of screen height at center x, and performs the swipe gesture using the helper function 'swipe'.
    @mcp.tool()
    def scroll_up(device_serial: str | None = None) -> str:
        """Scroll up on the current screen"""
        specs = get_screen_specs(device_serial)
        center_x = specs['width_px'] // 2
        start_y = int(specs['height_px'] * 0.3)
        end_y = int(specs['height_px'] * 0.7)
        return swipe(center_x, start_y, center_x, end_y, 300, device_serial)
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. While 'scroll up' implies a UI interaction, it doesn't specify what 'current screen' means (which app/context), whether scrolling has limits, what happens at the top, or if it requires specific UI elements to be present. Significant behavioral context is missing.

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, efficient sentence that states the core functionality upfront with zero wasted words. It's appropriately sized for a simple scrolling operation and gets straight to the point.

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?

Given the tool's simplicity (one optional parameter) and presence of an output schema (which handles return values), the description is minimally adequate. However, for a UI interaction tool with no annotations, it should provide more context about scrolling behavior, limitations, and when it can be used versus alternatives.

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%, but the parameter 'device_serial' is self-explanatory for device targeting. The description doesn't mention this parameter at all, but since there's only one optional parameter with a clear name, the baseline is appropriate. No additional parameter semantics are provided beyond what the schema name implies.

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 'Scroll up on the current screen' clearly states the action (scroll up) and target (current screen), providing a specific verb+resource combination. However, it doesn't differentiate from its sibling 'scroll_down' beyond the direction, missing explicit distinction.

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 about when to use this tool versus alternatives like 'scroll_down' or 'scroll_to_text'. The description only states what it does, not when it's appropriate or what prerequisites might exist for scrolling functionality.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/rahulkr/r_adb_mcp_server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server