Skip to main content
Glama
Sign In
wechat-mcp

wechat-mcp

by RungePei
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

wechat_get_recent_sessions

Get recent WeChat conversations with names, last messages, and timestamps, filtered by Today, Yesterday, Week, Month, or Year and optionally restricted to chats with 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": "wechat_get_recent_sessions"
  }
}

Input Schema

NameRequiredDescriptionDefault
recentNoToday | Yesterday | Week | Month | Year，也支持“今天”“本周”等中文Today
chat_onlyNo是否只返回有消息的会话

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.1/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. It discloses the shape of returned items (name, last message, time), but says nothing about ordering, pagination, or scope limits, and gives no explicit read-only/side-effect confirmation for an agent that might otherwise assume it touches messages.

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 compact sentence with the resource front-loaded and return contents tucked into a parenthetical. Nothing is redundant and nothing needs to be moved earlier.

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

Completeness3/5

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

With an output schema covering return values and full schema coverage on both parameters, the core call information is present. What is missing is usage context relative to the many read siblings (check_new_messages, get_chat_history), which leaves the agent to guess at routing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%: both 'recent' (with its English/Chinese time-range values) and 'chat_only' are fully documented in the schema. The description adds no parameter-level meaning beyond that, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb (获取) and resource (会话列表中的最近会话) and even names the returned fields (名称、最后一条消息与时间). It is clearly distinguishable from write-oriented siblings, though it does not explicitly separate itself from the closest read siblings like wechat_check_new_messages or wechat_get_chat_history.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use statement, no prerequisites, and no mention of alternatives. The agent must infer that this is the tool for browsing the recent session list rather than for fetching message content.

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