Skip to main content
Glama

模拟器原生交互

wdt_native

Executes native WeChat DevTools actions such as navigating home/back, handling modals, authorization prompts, payment/share dialogs, and switching tabBar tabs during mini program automation.

Instructions

执行原生层动作:goHome / navigateLeft / confirmModal / cancelModal / authorizeAllow / authorizeCancel / closePaymentDialog / shareCancel / shareConfirm / switchTab。

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": {
      "action": "<action>"
    },
    "name": "wdt_native"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlNoswitchTab 需要的 tabBar 路径
actionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.2

TDQS

C2.6/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full disclosure burden, yet it says nothing about side effects, whether actions wait for completion, what happens on failure, or what is returned. Names like confirmModal and closePaymentDialog imply UI mutation, but reversibility, timing, and error behavior are entirely undisclosed.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is a single front-loaded sentence with no filler, which is good. However, nearly the whole sentence is a verbatim copy of the schema enum, so its brevity reflects duplication rather than efficient communication.

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?

For a ten-action native interaction tool with no annotations and no output schema, the definition is thin: individual actions are never explained, preconditions (login state, open page, pending modal) are unstated, and return/error behavior is absent. An agent could pick an action but not predict its effect.

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?

With only 50% schema description coverage, the description should compensate, but it merely restates the action enum already present in the schema and says nothing about the url parameter or how it pairs with switchTab. No added meaning beyond the structured fields.

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 names a specific verb+resource ('执行原生层动作') and enumerates the concrete action set, so an agent knows this is the native-layer interaction dispatcher rather than a DOM/page tool. It does not differentiate itself from plausible siblings such as wdt_navigate or wdt_wx_method, so it stops short of a 5.

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?

There is no statement of when to choose this tool over wdt_navigate, wdt_element, or wdt_wx_method, nor which situations require each native action. The list of action names is the only hint, leaving selection to inference.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.