Skip to main content
Glama
Sign In
WeChat MCP Server

WeChat MCP Server

by CheserEri
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

get_wechat_status

Check if WeChat desktop client is connected, window is visible, and automation backend is available before sending or reading messages.

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": "get_wechat_status"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

A4/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full disclosure burden. It does make clear this is a non-mutating status probe by enumerating what is inspected, but it says nothing about cost, latency, or whether probing can affect the client or automation backend.

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?

A single front-loaded sentence with no filler, listing the three checks in a compact parallel structure. Nothing is wasted.

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 probe with an output schema already describing the return payload, the description covers the necessary scope. The only real omission is guidance on how to react to a negative result.

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 there is no parameter semantics to document; the baseline for a no-arg tool is 4.

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?

Names a specific verb (检查) and resource (微信客户端状态) and enumerates the three concrete aspects checked: connection status, window visibility, and automation backend availability. This is immediately distinguishable from every sibling, all of which operate on chats, messages, or contacts.

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 diagnostic nature implies a preflight use (verify WeChat is reachable before calling send_message or get_chat_list), but the description never states when to call it, when not to, or what to do if a check fails. Usage must be inferred from the content of the checks.

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

Deploy Server

Other Tools