Skip to main content
Glama
wechat-localmind

wechat-localmind

by qilaidev

wechat_list_chats

Read-onlyIdempotent

List accessible WeChat direct, group, and official-account chat sessions with IDs, names, types, message cursors, and member counts; filter by keyword or session type.

Instructions

List accessible macOS/Windows WeChat chat sessions across 1-on-1 direct chats (wxid_* / custom aliases / filehelper), group chats (@chatroom / @im.chatroom), and official accounts (gh_*), including chat_id, chat_name, chat_type, latest_msg_id cursor, 24h message count, and member count.

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_list_chats"
  }
}

Input Schema

NameRequiredDescriptionDefault
freshNoForce immediate SQLCipher decryption and SQLite snapshot refresh.
formatNojson
keywordNoOptional case-insensitive keyword filter for chat name, wxid, or alias.
chat_typeNoFilter by session type: 'all' (default), 'direct', 'group', or 'official'.all
include_blockedNoWhether to include chats blocked by current scope or blacklist/whitelist policy.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv2.0.0

TDQS

A4/5.0
Behavior4/5

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

The annotations already establish read-only, idempotent, non-destructive, closed-world behavior. Beyond them, the description adds supported desktop platforms, accessibility scoping, concrete identifier families, and result metadata such as the cursor and 24-hour activity count, though access prerequisites and normal-versus-fresh snapshot behavior remain unexplained.

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 single sentence is front-loaded, moving directly from action to platform and session scope to returned fields, with no filler. Its parenthetical identifier lists make it dense, but each detail helps disambiguate the supported session types.

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 a read-only list tool with five optional parameters, the description, schema, and annotations provide enough information to enumerate sessions and understand the principal returned fields despite the absence of an output schema. It would be more complete with an explicit discovery-to-message-retrieval workflow and a brief explanation of snapshot freshness and cursor usage.

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?

With 80% schema coverage, the schema already carries most of the parameter-documentation burden. The wxid_*, @chatroom, and gh_* examples usefully supplement chat_type, but the description adds little further meaning for fresh, format, keyword, or include_blocked.

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?

“List accessible macOS/Windows WeChat chat sessions” supplies a precise verb, resource, platform, and visibility scope. Covering direct, group, and official-account sessions and returning session metadata makes clear that this is broad session enumeration, not group-only listing or message retrieval.

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

Usage Guidelines3/5

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

The returned chat_id and latest_msg_id fields imply a session-discovery workflow, so the intended use is inferable. However, there is no explicit when-to-use or when-not guidance, no named alternative, and no explanation of how the cursor should be consumed.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.