Skip to main content
Glama
Sign In
Wechat Devtools MCP

Wechat Devtools MCP

by pureia
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

element_swipe_to

Swipes a swiper element to a specified slide index in a WeChat mini-program, enabling programmatic navigation to target content.

Instructions

滑动 swiper 到指定滑块

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>",
      "index": "<index>"
    },
    "name": "element_swipe_to"
  }
}

Input Schema

NameRequiredDescriptionDefault
indexYes目标滑块 index（仅 swiper 可用）
element_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.0.2

TDQS

C2.8/5.0
Behavior2/5

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

With no annotations, the description must disclose behavioral traits but does not. It only describes the action and fails to mention side effects, prerequisites, return values, or whether the swipe is simulated or triggers events.

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, focused sentence with no filler. It is concise and front-loaded, making it easy to parse quickly.

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 large set of sibling element tools and the absence of annotations or output schema, the description is too terse to fully support correct invocation. It lacks usage conditions, parameter details, and behavioral context needed for reliable tool selection.

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

Parameters2/5

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

The description adds no explicit parameter guidance. The 'index' parameter is already described in the schema ('目标滑块 index'), and 'element_id' remains unexplained; the description only implies the element is a swiper.

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 '滑动 swiper 到指定滑块' clearly identifies a swipe action on a swiper component to a target slide. It uses a specific verb and resource, but does not explicitly distinguish itself from similar sibling tools like element_slide_to.

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?

No guidance is provided on when to use this tool versus alternatives. The description only states the action, leaving the agent without criteria to choose between element_swipe_to and other element interaction tools such as element_slide_to or element_scroll_to.

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