Retrieve a list of recently received WeChat messages. Default returns 50 messages.
获取最近收到的消息列表。默认返回最近 50 条。
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_get_messages"
}
}| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | 返回条数（默认 50） |
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description doesn't explicitly state that this is a read-only operation or describe side effects (e.g., whether it marks messages as read). It only mentions the default limit of 50, leaving behavioral traits undisclosed.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is two short sentences, front-loaded with the core action, and contains no filler.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a low-complexity tool with no output schema, the description gives only a high-level view of the return value ('list of messages') without specifying message structure or other relevant behavior, making it partially incomplete.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The schema already documents the 'limit' parameter with its default (50), and the description repeats that same information without adding new semantics.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states 'Get a list of recently received messages' with a specific verb and resource, distinguishing it from sibling tools like wechat_send_text and wechat_search_messages.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description implies usage but doesn't explicitly provide when-to-use vs alternatives. It doesn't mention that wechat_search_messages should be used for searching, so guidance is lacking.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.