Skip to main content
Glama

断开自动化连接

wdt_disconnect

Disconnects the WebSocket automation session from WeChat DevTools; set closeProject=true to also close the project window without exiting DevTools.

Instructions

关闭 WebSocket 自动化连接;closeProject=true 时同时关闭项目窗口。不会退出开发者工具。

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_disconnect"
  }
}

Input Schema

NameRequiredDescriptionDefault
closeProjectNo是否同时关闭项目窗口

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.2

TDQS

A4/5.0
Behavior4/5

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

With no annotations provided, the description carries the behavioral disclosure burden. It clearly states the main effect (closing the WebSocket automation connection), the conditional side effect (closing the project window when closeProject=true), and an important non-effect (it does not exit the developer tools).

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 one compact sentence with three clear clauses, front-loading the primary action and then the conditional behavior and non-effect. There is no redundant or filler wording.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple one-parameter disconnect tool with no output schema and no annotations, the description covers the essential purpose, the optional project-window behavior, and the key non-effect. It does not describe edge cases such as already being disconnected, but none of those are critical to selecting or invoking the tool correctly.

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?

The schema fully documents the single closeProject parameter as meaning whether to also close the project window. The description repeats the same meaning with the true-case behavior, without adding syntax, default behavior, or other detail beyond the schema.

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 states a specific verb and resource: closing the WebSocket automation connection. It also scopes the effect with the conditional project-window closure and explicitly distinguishes itself from terminating the developer tools entirely.

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?

Usage is implied by the action: call this to disconnect automation, optionally closing the project window. The note that it will not exit the developer tools is useful contextual guidance, but no alternative tool such as wdt_quit is explicitly named as the choice for full termination.

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