Skip to main content
Glama
Sign In
AutoMobile

AutoMobile

by zillow
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript

scroll

Scrolls within mobile app containers to navigate content or locate specific elements by text or selector during automated testing.

Instructions

Scroll in a direction on a scrollable container, optionally to find an element (supports text and selectors)

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": {
      "containerElementId": "<containerElementId>",
      "direction": "<direction>",
      "platform": "<platform>"
    },
    "name": "scroll"
  }
}

Input Schema

NameRequiredDescriptionDefault
containerElementIdYesElement ID to scroll until visible
directionYesScroll direction
lookForNoWhat we're searching for while scrolling
speedNoScroll speed
platformYesPlatform of the device

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations provided, the description carries full burden but offers minimal behavioral disclosure. It mentions scrolling 'to find an element' but doesn't describe what happens when found/not found, error conditions, performance characteristics, or side effects. The agent must infer behavior from the tool name and parameters alone.

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?

The description is a single, efficient sentence that communicates the core functionality. However, it could be more front-loaded by explicitly stating the primary purpose before the optional capabilities.

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 tool with 5 parameters, no annotations, and no output schema, the description is insufficient. It doesn't explain what the tool returns, how errors are handled, or the interaction between scrolling and element-finding. The agent lacks critical context for proper invocation.

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 100%, so the schema fully documents all 5 parameters. The description adds marginal value by mentioning 'supports text and selectors' which relates to the 'lookFor' parameter, but doesn't provide additional semantic context beyond what's already in the schema descriptions.

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 action ('scroll') and target ('scrollable container'), and mentions the optional element-finding capability. It distinguishes from siblings like 'swipe' or 'swipeOnElement' by focusing on scrolling within containers, but doesn't explicitly contrast with similar tools.

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 like 'swipe' or 'swipeOnElement', nor does it mention prerequisites or contextual constraints. It simply states what the tool does without usage context.

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