Skip to main content
Glama
Sign In
Wechat Devtools MCP

Wechat Devtools MCP

by pureia
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

element_property

Retrieve a specified property value from a WeChat mini-program element, such as an input's value, to validate states and drive automation checks.

Instructions

获取元素属性值（如 input 组件的 value）

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

Input Schema

NameRequiredDescriptionDefault
nameYes属性名，如 input 组件的 value
element_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.0.2

TDQS

B3.1/5.0
Behavior2/5

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

With no annotations, the description must carry the full burden of behavioral disclosure. It is a getter, which implies a read-only operation, but the description does not mention any side-effects, return format, or error behavior. It merely restates the basic function.

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, efficient sentence that immediately conveys the core purpose with an example. 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?

For a simple getter with two parameters and no output schema, the description provides the essential idea, but it lacks differentiation from closely related sibling tools and doesn't clarify expected return behavior. It is minimally viable but leaves contextual gaps.

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?

Schema description coverage is only 50% (name described, element_id not). The description adds a clarifying example for the 'name' parameter ('如 input 组件的 value'), but element_id remains underspecified. This partially compensates for the schema gap but not fully.

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 clearly states the tool's function: '获取元素属性值' (get element attribute value) with a concrete example. However, it does not differentiate from sibling tools like element_attribute or element_value, which likely overlap significantly.

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 such as element_attribute or element_value. The description only states what it does, not when to choose it.

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