Skip to main content
Glama

get_group_msg_history

Read-only

Retrieve QQ group chat message history from the latest message or around a specific message ID, with controls for count and older or newer message paging.

Instructions

获取群消息历史 省略 message_id 从最新消息开始;翻页使用上一页实际 message_id,不要自行加减。 Returns: { messages }:群消息事件对象数组(每项为 OneBot 消息事件,内部字段不固定)。

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "group_id": "<group_id>"
    },
    "name": "get_group_msg_history"
  }
}

Input Schema

NameRequiredDescriptionDefault
countNo
group_idYes群号
message_idNo
reverse_orderNo仅在 message_id 非 0 时生效;true 返回锚点及更旧消息,false 返回锚点及更新消息

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already establish it as a read-only, open-world, non-destructive query, so the safety profile is covered. The description adds useful behavioral detail: the pagination anchor semantics and the caveat that message event fields are not fixed across items. It says nothing about count limits, ordering guarantees, or failure cases (e.g. invalid message_id).

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?

Two compact sentences plus a short return-shape note; the pagination rule is front-loaded after the purpose. The mixed-language phrasing is dense but no sentence is redundant.

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 supplies the return shape ({ messages } array of OneBot event objects) and warns about variable item fields, which is what an agent needs to consume the result. Only the count parameter and error conditions remain unaddressed.

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 coverage is 50%, and the description compensates for the undocumented message_id by explaining its default behavior (omitted = latest) and pagination role. However, count is undocumented in both schema and description, so it does not fully close the gap.

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 opening '获取群消息历史' gives a concrete verb+resource, and the name itself separates it from get_friend_msg_history and get_group_system_msg. It stops short of explicitly contrasting those siblings, but the scope is unambiguous.

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

Usage Guidelines4/5

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

It specifies the default entry point (omit message_id to start from the newest message) and prescribes pagination behavior, including a corrective warning not to arithmetic-adjust message_id. It does not name alternative tools, but usage mechanics are clear.

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