WeChat FastBridge
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| wechat_statusB | Check readiness. |
| wechat_readB | Read a chat; with after, return its delta and smart context. |
| wechat_send | Send verified text. |
| wechat_send_media | Send one verified file or sticker. |
| wechat_waitC | Wait for one chat's delta and smart context. |
| wechat_inbox_wait | Wait for changed previews in allowed chats. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 3 tools
Tools 'wechat_read' and 'wechat_wait' both deal with delta and smart context, and their descriptions are too similar, causing potential confusion. 'wechat_status' is distinct.
All tool names follow a consistent 'wechat_verb' pattern with snake_case, which is clear and predictable. Minor deviation is that verbs are not part of a full verb_noun structure, but overall consistent.
Only 3 tools for a messaging bridge server feels too few. Core operations like sending messages or managing chats are missing, making the set feel thin.
The tool surface is severely incomplete for a WeChat bridge. It lacks essential operations such as sending messages, listing chats, or managing contacts. Only read/wait and a status check are provided.