Skip to main content
Glama

关闭项目窗口

wdt_close_project
Destructive

Closes a specified WeChat Mini Program project window without exiting the entire WeChat DevTools instance, so you can manage individual projects while keeping the IDE open.

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

Input Schema

NameRequiredDescriptionDefault
projectPathNo小程序项目目录;省略时使用 WECHAT_DEVTOOLS_PROJECT

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.2

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, so the safety profile is known. The description adds the useful scoping fact that the devtools process itself survives the close, but it says nothing about unsaved state, running builds, or what the caller observes afterwards. Useful context, but modest beyond the annotation.

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?

One short sentence with the action front-loaded and the scope qualifier second; every clause earns its place and nothing is padded.

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 single-optional-parameter, annotation-covered tool with no output schema, the definition covers what the tool does and what it does not do. Only side-effect details on existing project state are absent, which is a minor gap at this complexity.

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?

Schema description coverage is 100% and the single optional projectPath parameter already documents its meaning and the WECHAT_DEVTOOLS_PROJECT fallback. The description only echoes that a project window is targeted, adding no format or selection detail beyond the schema, so the baseline of 3 applies.

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?

States a specific verb and resource ("关闭指定项目窗口") and immediately bounds the scope with "不退出整个开发者工具", so an agent can tell it apart from a full devtools shutdown. It stops short of naming the sibling that does the full shutdown, so differentiation is implied rather than explicit.

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 clause "不退出整个开发者工具" implies the selection rule: use this when only one project window should be closed, and by negation something else handles quitting the tool. However, no alternative tool is named and no preconditions (e.g., whether the window must be open, whether a build may be in progress) are given.

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