Touchpoint

Overview Schema Source Related Servers Discussions Admin

scroll

Scroll by mouse wheel ticks at the current cursor location or at a specified element. Choose direction (up, down, left, right) and tick count.

Instructions

Scroll by mouse wheel ticks.

With ``element_id``, moves the cursor to that element's position
first, then scrolls — useful for scrolling inside a specific list,
panel, or container.  Without it, scrolls at the current cursor
position.

Args:
    direction: One of "up", "down", "left", "right".
    amount: Number of scroll ticks (default 3).
    element_id: Optional element to scroll at.  When given, cursor
        is moved to the element's center first.

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

Input Schema

Name	Required	Description	Default
`direction`	Yes
`amount`	No
`element_id`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv0.3.0Jun 15, 2026

addedInput schema / properties / element_id

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Element Id"
+}

First observedv0.1.0Mar 24, 2026

TDQS

A4.6/5.0

Behavior4/5

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

With no annotations, the description carries the full burden. It transparently discloses that with element_id, the cursor is moved to the element's center first before scrolling. It does not mention potential side effects like permanent cursor movement or scroll boundaries, but the behavior is adequately described for a simple scroll action.

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 concise and well-structured: a one-line summary followed by a terse paragraph explaining behavior with and without element_id, then a clean parameter listing. No superfluous text; every sentence adds value.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple scrolling tool with an output schema (which handles return value documentation), the description covers all essential aspects: what it does, parameter meanings, and behavioral nuance. It is sufficiently complete for an agent to invoke the tool correctly.

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

Parameters5/5

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

The schema provides only property names and types with no descriptions. The description adds critical meaning: it defines direction values as 'up', 'down', 'left', 'right', explains amount as 'Number of scroll ticks (default 3)', and clarifies element_id as optional and that it causes cursor movement. This fully compensates for the 0% schema coverage.

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 starts with 'Scroll by mouse wheel ticks,' which clearly states the tool's core action and resource. It distinguishes between scrolling with an element_id (for scrolling inside a container) and without, making its purpose specific and unambiguous.

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

Usage Guidelines4/5

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

The description provides clear guidance on when to use the element_id parameter (for scrolling inside a specific list, panel, or container) versus without (scroll at current cursor position). However, it does not explicitly compare with sibling tools or state when not to use this tool.

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