Skip to main content
Glama

退出开发者工具

wdt_quit
Destructive

Closes all project windows and exits the entire WeChat DevTools session, useful when you need to fully shut down the IDE after automation tasks.

Instructions

退出整个微信开发者工具。会关闭所有项目窗口。

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.2

TDQS

A3.9/5.0
Behavior4/5

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

destructiveHint=true already tells the agent this is a destructive call, so the description's added job is to say what is destroyed — and "会关闭所有项目窗口" does exactly that, making the blast radius concrete. It still omits whether unsaved changes are lost or whether the call waits for/confirms termination, which would be the remaining valuable detail.

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?

Two short sentences, zero filler, with the resource and its scope established first and the side effect immediately after. Nothing is redundant with the name or the annotations.

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 zero-parameter, destructive termination tool, the definition covers what it does, how broad the effect is, and the annotations carry the safety classification. The only gap an agent might care about — whether quitting is graceful or whether state is preserved — is unaddressed.

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 there is nothing for the description to clarify beyond the schema; baseline applies. Adding a note that no confirmation argument exists (call is immediate) would be the only possible improvement.

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?

"退出整个微信开发者工具" names a specific verb (quit) and resource (the whole DevTools instance), and "会关闭所有项目窗口" makes the scope explicit so it is distinguishable from a single-project close. It stops short of naming wdt_close_project as the narrower sibling, so the differentiation is implied by scope rather than stated.

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 word "整个" and "会关闭所有项目窗口" imply the agent should only call this when it intends to shut everything down, which is useful implied guidance. However, there is no explicit when-to-use/when-not statement and no pointer to wdt_close_project for the far more common case of closing one project window.

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