Skip to main content
Glama

get_group_system_msg

Read-only

Retrieve QQ group system messages, including join requests, inviters, and handlers, and filter by group ID or pending status to review or process membership actions.

Instructions

获取群系统消息 将 group_id 替换为当前账号可访问的群号。 Returns: 群系统消息数组,分别提供入群者、邀请人和处理者,可按群号或未处理状态过滤。身份为 0 时须查看状态;未知不代表不存在邀请人。

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": "get_group_system_msg"
  }
}

Input Schema

NameRequiredDescriptionDefault
countNo每个收件箱最多读取的记录数
group_idNo
only_pendingNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds genuine behavioral value by describing the shape of the returned array and a result-interpretation caveat ('unknown does not mean no inviter exists'), which warns against false negatives. It stops short of explaining ordering, volume limits per inbox, or what 'identity is 0' refers to.

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?

Compact and front-loaded: purpose, then a 'Returns:' block describing output fields. The final clause about identity 0 is terse to the point of being cryptic, but no sentence is filler.

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?

No output schema exists, so the description must carry return semantics, and it does at a high level (array with joiner, inviter, handler). However, the identity-0 caveat is unexplained — it is unclear which field or actor it refers to — and pagination/volume behavior across inboxes is not addressed, leaving gaps for a zero-required-parameter read tool with three filters.

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

Parameters4/5

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

Schema description coverage is only 33%: count is documented in the schema, but group_id and only_pending are bare. The description compensates by explaining that group_id must be a group reachable by the current account and that the results can be filtered by group number or unhandled status, effectively covering both undocumented parameters.

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?

The first clause restates the tool name, but the Returns sentence concretely defines what a 'system message' is here: joiners, inviters and handlers in a per-group array. That distinguishes it from siblings like get_group_msg_history or get_group_notice without naming them.

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?

It states a prerequisite ('replace group_id with a group number the current account can access') and that results can be filtered by group or pending state, which implies the pending-review use case. It never says when to prefer this over related siblings such as get_group_ignored_notifies or get_group_ignore_add_request, and gives no when-not guidance.

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