Skip to main content
Glama
Sign In
wechat-mcp

wechat-mcp

by jimingyuan7
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Log in to WeChat via QR code

wechat_login

Initiate WeChat login by scanning a QR code printed to the terminal. Wait for confirmation from the WeChat mobile app to return the connected account ID.

Instructions

Start an interactive WeChat login. A QR code is printed to the server's STDERR/terminal; scan it with the WeChat mobile app and confirm. Blocks until login completes or times out. For first-time setup it is usually easier to run npm run login in a real terminal. Returns the connected account id on success.

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

Input Schema

NameRequiredDescriptionDefault
timeoutMsNoMax time to wait for the QR scan (default 480000 = 8 min).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations, the description carries full burden. It discloses blocking behavior, QR code output to STDERR, need for mobile app scanning, and return of account id on success. It lacks details on failure modes or prerequisites.

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?

The description is concise with two main sentences covering purpose, behavior, and an alternative approach. No unnecessary words, front-loaded with the core action.

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 an interactive login tool, the description covers the process, blocking, and return value. It lacks output schema but states the return. Could mention error handling or cancellation, but overall sufficient.

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?

Schema coverage is 100% with description for timeoutMs. The description adds context by mentioning the default timeout (8 minutes) and the blocking nature, which complements the schema.

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?

The description clearly states the tool logs in to WeChat via QR code, specifying the verb (login) and resource (WeChat). It distinguishes from sibling tools like wechat_list_accounts, wechat_logout, etc., by describing the interactive login process.

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?

Provides guidance that for first-time setup, running 'npm run login' in a real terminal is easier, indicating when not to use this tool. However, it does not explicitly list alternative tool uses or when to prefer this tool over others.

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