Skip to main content
Glama
Sign In
mobilerun-mcp

mobilerun-mcp

by impeterwayne
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Scroll Right

scroll_right

Reveal off-screen content to the right by scrolling the device screen horizontally.

Instructions

Scroll the content right (reveal what is to the right).

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_right"
  }
}

Input Schema

NameRequiredDescriptionDefault
amountNo
deviceNo
som_idNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior3/5

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

With no annotations provided, the description carries full behavioral disclosure burden. It does state the intended observable effect—scroll right and reveal content to the right—but it does not disclose how the amount parameter affects the scroll, whether the scroll is smooth, or how device/som_id scoping works.

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 sentence with no filler. The parenthetical earns its place by clarifying the direction and purpose, and the entire definition is appropriately sized for such a simple tool.

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?

Although the tool is simple and an output schema exists, the definition is incomplete because it leaves all parameter semantics unexplained and offers no guidance for choosing this tool over related scroll/swipe tools. An agent would not know what amount=0.5 means or whether device/som_id are needed.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% and the description adds no meaning for any of the three parameters (amount, device, som_id). The default 0.5 for amount is unexplained, and device/som_id are completely undocumented, leaving the agent to guess their semantics.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses a specific verb 'Scroll' with a clear object 'the content' and direction 'right', and the parenthetical 'reveal what is to the right' reinforces the intended outcome. This clearly distinguishes it from siblings like scroll_left, scroll_down, and scroll_up.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage when content is clipped or hidden on the right side, but it does not explicitly state when to use this tool versus alternatives like scroll_to, swipe, or the other directional scroll tools. It gives context but no exclusions or routing guidance.

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