Skip to main content
Glama

连接已开启的自动化端口

wdt_auto_connect

Connects to an existing WeChat DevTools automation WebSocket port without starting the IDE, letting agents control an already-open DevTools session.

Instructions

不启动 IDE,直接连接一个已经用 auto 模式打开的自动化端口。

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

Input Schema

NameRequiredDescriptionDefault
timeoutMsNo连接超时,默认 30000
wsEndpointNo默认 ws://127.0.0.1:9420

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.2

TDQS

B3.4/5.0
Behavior3/5

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

No annotations are supplied, so the description bears the full load. It discloses one useful behavioral fact, that it attaches to an existing port without launching the IDE, but says nothing about failure behavior when no port is listening, whether it replaces or coexists with an existing session, or what a successful connect yields.

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?

A single compact sentence with the key constraint front-loaded and no wasted wording. It is efficient, though the brevity leaves behavioral gaps that the other dimensions penalize rather than this one.

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?

For a simple two-optional-parameter connection tool with fully documented schema and no output schema, the definition covers the basic purpose. It is still thin on error conditions and connection lifecycle, which matter for an agent deciding whether connecting is safe at a given moment.

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 both parameters are optional with documented defaults (30000 ms timeout, ws://127.0.0.1:9420). The description adds no meaning 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?

The description states a specific verb and resource: connect to an automation port that is already open in auto mode, and explicitly notes it does not start the IDE. This sets it apart from wdt_auto_start in practice, though no sibling is named.

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 precondition 'already opened with auto mode' implies when this tool applies, and the phrase 'does not start the IDE' distinguishes it from a start action. However, it never explicitly tells the agent to use wdt_auto_start when no port is open, nor what to do if no port exists.

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