Skip to main content
Glama
Sign In
Wechat Devtools MCP

Wechat Devtools MCP

by pureia
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

element_text

Retrieve the text content from an element in a WeChat mini-program using its element ID.

Instructions

获取元素文本内容

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": "element_text"
  }
}

Input Schema

NameRequiredDescriptionDefault
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?

No annotations are provided, so the description carries full responsibility for transparency. It only states the action and does not disclose read-only behavior, return format, error handling, or side effects. The word 'get' subtly implies a read operation, but this is minimal and not sufficient for a tool with no annotation support.

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 phrase with no filler or irrelevant information. It is front-loaded and appropriately brief given the simplicity of the 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?

The tool is simple, but the description is minimal. It fails to describe the return value (the text content itself) or any edge cases, and with no output schema to fill gaps, an agent lacks crucial context for handling the tool's result.

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

Parameters1/5

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

The input schema has one parameter (element_id) with 0% description coverage. The description does not mention element_id, how to obtain it, or its expected format, providing no added value beyond the schema's raw type information.

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 '获取元素文本内容' (Get element text content) uses a specific verb and resource, clearly distinguishing it from sibling tools like element_attribute or element_value. It is unambiguous about what the tool does.

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

Usage Guidelines3/5

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

There is no explicit guidance on when to use this tool versus alternatives. The description implies usage for reading an element's text content, but it does not mention exclusions or alternative tools, making it merely implied rather than explicit.

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