Skip to main content
Glama
Sign In
Wechat Devtools MCP

Wechat Devtools MCP

by pureia
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

element_slide_to

Set a slider component's value in a WeChat mini-program by providing the element ID and target numeric value.

Instructions

设置 slider 组件的值

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>",
      "value": "<value>"
    },
    "name": "element_slide_to"
  }
}

Input Schema

NameRequiredDescriptionDefault
valueYes要设置的值（仅 slider 可用）
element_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.0.2

TDQS

C2.9/5.0
Behavior1/5

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

The description discloses no behavioral traits beyond the basic operation. It does not mention side effects (e.g., triggering change events), validation (e.g., value range), or behavior when the element is not a slider. With no annotations to provide context, this is a significant gap.

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, front-loaded sentence that directly states the purpose without superfluous words. It is appropriately concise for 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?

Given the simplicity of the tool, the description still falls short. It does not explain when to use it (e.g., after identifying a slider), potential error conditions, or the effect of setting a value. The lack of annotations and output schema makes the description insufficient for confident usage.

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?

Schema coverage is 50%, with only 'value' described. The description adds the 'slider' context but does not explain 'element_id' (e.g., what identifier to use) or clarify the expected format or constraints for the value, leaving the undocumented parameter ambiguous.

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 '设置 slider 组件的值' clearly states the action (set value) and the resource (slider component). It distinguishes itself from siblings like element_input (text input) and element_swipe_to (gesture operation) by specifying the slider context.

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 does not mention prerequisites, such as requiring a slider element, or explicitly contrast with similar operations like element_input or element_set_data.

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