Skip to main content
Glama

微信开发者工具环境状态

wdt_status
Read-only

Check the WeChat DevTools path, service port toggle, automation connection status, and port occupancy before operations to diagnose setup or connectivity issues.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.2

TDQS

A3.9/5.0
Behavior3/5

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

readOnlyHint=true already tells the agent this is a safe, non-mutating call, so the annotation carries the safety profile. The description adds the specific diagnostics being inspected (port occupancy, connection state), which is useful, but it says nothing about cost, latency, or how the results are shaped. Adequate rather than rich, given the annotation coverage.

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 with no filler, and the list of inspected items is front-loaded ahead of the usage hint. Every clause contributes information.

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?

There is no output schema, so the description reasonably carries the return-value burden by naming the four things it reports. It is nearly complete for a zero-parameter status check, with only minor gaps around result format.

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 zero parameters, so the baseline is 4 and there is no parameter meaning the description needs to compensate for. Nothing in the description conflicts with the empty schema.

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 concrete verb (检查) and enumerates the exact resources inspected: devtools path, service-port toggle, automation connection state, and port occupancy. An agent can tell this is a diagnostic/status tool, though it does not explicitly contrast itself with adjacent tools such as wdt_system_info or wdt_is_login.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

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

"开始任何操作前可先调用" gives clear preflight guidance on when to reach for this tool. It stops short of stating exclusions or naming alternatives for the cases it does not cover, so it lands just below the top band.

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