Skip to main content
Glama
wechat-localmind

wechat-localmind

by qilaidev

wechat_list_groups

Read-onlyIdempotent

Lists accessible WeChat group chats with chat IDs, names, latest message cursors, 24-hour message counts, and member counts, with optional keyword filtering.

Instructions

List accessible macOS/Windows WeChat group chats (@chatroom / @im.chatroom), including chat_id, group_name, 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_groups"
  }
}

Input Schema

NameRequiredDescriptionDefault
freshNoForce immediate SQLCipher decryption and SQLite snapshot refresh.
formatNojson
keywordNoOptional case-insensitive keyword filter for group name.
include_blockedNoWhether to include groups blocked by blacklist/whitelist policy.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description still adds value by naming the returned fields (chat_id, group_name, latest_msg_id cursor, 24h count, member count) and by flagging that only 'accessible' groups are exposed, which is not in the annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single dense sentence that front-loads the verb, target resource and platform, then enumerates returned fields. No filler, though the field enumeration makes it long and a comma-separated list would scan faster.

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?

With no output schema, the description compensates by listing the return fields and the cursor, and the four optional params are mostly documented in the schema. It would be complete if it clarified pagination via latest_msg_id and the blacklist/whitelist behavior behind include_blocked.

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 75%, so the schema already explains fresh, keyword, include_blocked and format. The description adds no parameter-level meaning, such as what 'fresh' costs in decryption time or how include_blocked interacts with the 'accessible' wording, leaving the 25% gap unfilled.

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 (List) and resource (WeChat group chats) plus the native identifiers @chatroom / @im.chatroom, so it is distinguishable from wechat_list_chats which handles other chat types. It stops short of explicitly naming that sibling as the alternative, so the differentiation relies on the word 'group'.

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?

Usage is implied: use it to enumerate group chats rather than per-conversation chats, and 'accessible' hints that policy-filtered groups matter. There is no explicit when-to-use/when-not guidance or named alternative, so an agent must infer the boundary with wechat_list_chats.

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