Skip to main content
Glama
Sign In
Wechat Devtools MCP

Wechat Devtools MCP

by pureia
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

element_scroll_to

Scroll a scroll-view to specified x, y coordinates by element ID, enabling precise UI testing in WeChat mini-programs.

Instructions

滚动 scroll-view 到指定位置

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": {
      "element_id": "<element_id>",
      "x": "<x>",
      "y": "<y>"
    },
    "name": "element_scroll_to"
  }
}

Input Schema

NameRequiredDescriptionDefault
xYes
yYes滚动位置（仅 scroll-view 可用）
element_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.0.2

TDQS

A3.7/5.0
Behavior2/5

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

There are no annotations, and the description only provides the basic action without disclosing side effects, prerequisites, or error behavior. It does not mention coordinate handling, smoothness, or what happens if the element is not a scroll-view.

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 concise sentence, front-loaded with the action and target. No wasted words.

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?

The tool is simple, but with no annotations or output schema, the description lacks details on return values, errors, and prerequisites. It does provide the key context of targeting scroll-view, but leaves out additional behavioral context.

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 schema has 33% description coverage (only y has a description). The description adds that the tool scrolls to a specified position, implying x and y are coordinates, but does not elaborate on element_id or coordinate system.

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 clearly states '滚动 scroll-view 到指定位置' (scroll scroll-view to specified position), specifying the verb 'scroll', the resource 'scroll-view', and the action's target. This distinguishes it from sibling tools like page_scroll_to and element_swipe_to.

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 identifies scroll-view as the target, giving clear context for when to use the tool. However, it does not explicitly state when not to use it or name alternative tools, making it less explicit than the highest bar.

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