Skip to main content
Glama
Sign In
wechat-mcp

wechat-mcp

by jimingyuan7
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Send a WeChat typing indicator

wechat_typing

Show or cancel the typing indicator to a WeChat user. Set status to 'typing' to indicate activity, or 'cancel' to clear it.

Instructions

Show (or cancel) the '正在输入…' typing indicator to a WeChat user. Useful before a slow reply so the user sees the bot is working. The required typing ticket is resolved automatically. If multiple accounts are logged in, pass accountId.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "to": "<to>"
    },
    "name": "wechat_typing"
  }
}

Input Schema

NameRequiredDescriptionDefault
toYesRecipient WeChat id, e.g. 'xxxx@im.wechat'.
statusNo'typing' to show the indicator (default), 'cancel' to clear it.
accountIdNoSending account id; required only when multiple accounts are logged in.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A4.3/5.0
Behavior3/5

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

No annotations provided, so description bears full burden. It mentions automatic ticket resolution but omits potential side effects like rate limits or session requirements.

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 succinct sentences that front-load the action and provide key usage context without extraneous detail.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple tool with 3 params fully described in schema, the description covers usage context and a practical tip. No output schema is needed for a side-effect tool.

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% (baseline 3). Description adds value by explaining accountId's conditional necessity and default status value, exceeding mere schema repetition.

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 title 'Send a WeChat typing indicator' and description 'Show (or cancel) the '正在输入…' typing indicator' clearly specify the action and resource. It is distinct from sibling tools like wechat_send and wechat_listen.

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?

The description explains when to use ('before a slow reply') and hints at accountId condition. However, it lacks explicit alternatives or when-not-to-use guidance.

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