Skip to main content
Glama
Wladastic

AutoProbeMCP

by Wladastic

check_scrollability

Verify page scrollability in vertical, horizontal, or both directions using AutoProbeMCP’s browser automation tool to ensure interactive web functionality.

Instructions

Check if the page is scrollable in the specified direction

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
directionNoDirection to check for scrollabilityboth

Implementation Reference

  • Defines the Zod schema for validating input parameters of the check_scrollability tool, specifying the direction to check ('vertical', 'horizontal', or 'both').
    const CheckScrollabilitySchema = z.object({
      direction: z.enum(['vertical', 'horizontal', 'both']).default('both')
    });
  • src/index.ts:387-401 (registration)
    Registers the check_scrollability tool in the MCP server's list of tools, providing its name, description, and input schema for the ListToolsRequest.
    {
      name: 'check_scrollability',
      description: 'Check if the page is scrollable in the specified direction',
      inputSchema: {
        type: 'object',
        properties: {
          direction: {
            type: 'string',
            enum: ['vertical', 'horizontal', 'both'],
            default: 'both',
            description: 'Direction to check for scrollability'
          }
        }
      }
    }
  • Handler function within the tool dispatch switch statement. Parses input, evaluates JavaScript on the page to compute document vs viewport dimensions and current scroll positions, determines scrollability in vertical/horizontal directions, and returns a formatted text response describing the scroll status.
              case 'check_scrollability': {
                if (!currentPage) {
                  throw new Error('No browser page available. Launch a browser first.');
                }
    
                const params = CheckScrollabilitySchema.parse(args);
                const { direction } = params;
    
                // Check scrollability with proper typing
                const scrollInfo = await currentPage.evaluate((dir) => {
                  const documentHeight = Math.max(
                    document.body.scrollHeight,
                    document.body.offsetHeight,
                    document.documentElement.clientHeight,
                    document.documentElement.scrollHeight,
                    document.documentElement.offsetHeight
                  );
                  
                  const documentWidth = Math.max(
                    document.body.scrollWidth,
                    document.body.offsetWidth,
                    document.documentElement.clientWidth,
                    document.documentElement.scrollWidth,
                    document.documentElement.offsetWidth
                  );
                  
                  const viewportHeight = window.innerHeight;
                  const viewportWidth = window.innerWidth;
                  
                  const verticalScrollable = documentHeight > viewportHeight;
                  const horizontalScrollable = documentWidth > viewportWidth;
                  
                  const currentScrollY = window.scrollY;
                  const currentScrollX = window.scrollX;
                  const maxScrollY = Math.max(0, documentHeight - viewportHeight);
                  const maxScrollX = Math.max(0, documentWidth - viewportWidth);
                  
                  const verticalInfo = {
                    scrollable: verticalScrollable,
                    currentPosition: currentScrollY,
                    maxScroll: maxScrollY,
                    canScrollDown: currentScrollY < maxScrollY,
                    canScrollUp: currentScrollY > 0
                  };
                  
                  const horizontalInfo = {
                    scrollable: horizontalScrollable,
                    currentPosition: currentScrollX,
                    maxScroll: maxScrollX,
                    canScrollRight: currentScrollX < maxScrollX,
                    canScrollLeft: currentScrollX > 0
                  };
                  
                  return {
                    direction: dir,
                    vertical: verticalInfo,
                    horizontal: horizontalInfo,
                    anyScrollable: verticalScrollable || horizontalScrollable
                  };
                }, direction);
    
                // Format the response message based on direction
                let message = '';
                
                if (direction === 'both') {
                  const v = scrollInfo.vertical;
                  const h = scrollInfo.horizontal;
                  message = `Page scrollability status:
    Vertical: ${v.scrollable ? 'Scrollable' : 'Not scrollable'}${v.scrollable ? ` (${v.currentPosition}/${v.maxScroll})` : ''}
    Horizontal: ${h.scrollable ? 'Scrollable' : 'Not scrollable'}${h.scrollable ? ` (${h.currentPosition}/${h.maxScroll})` : ''}
    Overall: ${scrollInfo.anyScrollable ? 'Page is scrollable' : 'Page is not scrollable'}`;
                } else if (direction === 'vertical') {
                  const v = scrollInfo.vertical;
                  message = `Vertical scrolling: ${v.scrollable ? 'Available' : 'Not available'}`;
                  if (v.scrollable) {
                    message += `\nPosition: ${v.currentPosition}/${v.maxScroll}`;
                    message += `\nCan scroll up: ${v.canScrollUp}`;
                    message += `\nCan scroll down: ${v.canScrollDown}`;
                  }
                } else {
                  const h = scrollInfo.horizontal;
                  message = `Horizontal scrolling: ${h.scrollable ? 'Available' : 'Not available'}`;
                  if (h.scrollable) {
                    message += `\nPosition: ${h.currentPosition}/${h.maxScroll}`;
                    message += `\nCan scroll left: ${h.canScrollLeft}`;
                    message += `\nCan scroll right: ${h.canScrollRight}`;
                  }
                }
    
                return {
                  content: [
                    {
                      type: 'text',
                      text: message
                    }
                  ]
                };
              }
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states what the tool does but lacks critical details: it doesn't specify the return format (e.g., boolean, scroll dimensions), error conditions (e.g., if no page is loaded), or performance implications (e.g., synchronous check). For a tool with zero annotation coverage, this is a significant gap in transparency.

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, clear sentence that efficiently conveys the core functionality without unnecessary words. It is front-loaded with the main action ('Check if the page is scrollable') and specifies the key constraint ('in the specified direction'). Every part of the sentence earns its place, making it highly concise and well-structured.

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?

Given the complexity of a browser interaction tool with no annotations and no output schema, the description is incomplete. It doesn't explain what the tool returns (e.g., a boolean or scrollable dimensions), how it interacts with the browser context, or potential limitations (e.g., only works on loaded pages). For a tool in this environment, more context is needed to be fully helpful.

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?

The input schema has 100% description coverage, with the single parameter 'direction' fully documented in the schema (including enum values and default). The description adds no additional parameter semantics beyond implying scrollability checking, which the schema already covers. This meets the baseline of 3 for high schema coverage without extra value from the description.

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 the tool's function as checking page scrollability in a specified direction, using specific verbs ('check if') and resources ('the page'). It distinguishes itself from siblings like 'scroll' (which performs scrolling) and 'get_page_info' (which retrieves page metadata). However, it doesn't explicitly contrast with all possible alternatives, keeping it at 4 rather than 5.

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?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., requiring a launched browser), exclusions (e.g., not applicable to non-scrollable elements), or comparisons with sibling tools like 'get_page_info' that might provide related information. This lack of contextual usage advice results in a low score.

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

Related 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/Wladastic/AutoProbeMCP'

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