Skip to main content
Glama

登录开发者工具

wdt_login

Triggers the official WeChat DevTools CLI login flow and prints a terminal QR code that users scan with WeChat to authenticate before running project or automation commands.

Instructions

触发官方 CLI 登录,stdout 中通常包含二维码(终端字符画)。需要用户用微信扫码。

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "wdt_login"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.2

TDQS

A3.5/5.0
Behavior3/5

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

The only annotation is openWorldHint=true, which conveys very little. The description usefully discloses that the QR code is emitted as terminal ASCII art on stdout and that a WeChat scan is required, which is meaningful workflow context. It does not say whether the call blocks until the scan completes, how long it waits before timing out, or what it returns if the terminal is not interactive.

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

Conciseness4/5

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

It consists of two short sentences and is front-loaded with the action, followed by the output detail and the user requirement. Every sentence carries information, with only minor terseness at the end.

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?

This is an interactive, human-in-the-loop operation, and there is no output schema, so the description must carry the full burden. It covers what happens and who must act, but it leaves out blocking behavior, timeout, and how to proceed after the scan finishes, which are gaps an agent would want filled.

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

Parameters4/5

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

The tool takes no parameters, so the baseline is 4. There are no arguments whose meaning the description would need to add.

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 states a specific verb and resource: it triggers the official CLI login. It is clear about the side effect, namely a QR code appearing on stdout. It does not name the sibling tool wdt_is_login, which tells the agent whether a login is already active, so it gets a 4 rather than 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 Guidelines3/5

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

The sentence '需要用户用微信扫码' implies the precondition that a human must scan a QR code with WeChat, and therefore when to use the tool. However, the description never says whether to check the login state first with wdt_is_login, or what to do if a login already exists. The guidance on when to use the tool is thus only implied.

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