Skip to main content
Glama
haoan33

OmniQQ-MCP

by haoan33
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

get_group_msg_history

Fetch historical chat records from a specified QQ group via NapCat, with pagination by count and message cursor for retrieving older messages.

Instructions

从 NapCat 获取指定群聊的历史聊天记录 (NapCat OneBot 11: get_group_msg_history)。 :param group_id: 群号 :param count: 获取的消息条数，默认 20 :param message_seq: 历史游标，填上一页最早记录的 message_id；NapCat 的参数名沿用 message_seq，但不要填返回记录的 message_seq。不填则取最新记录。 :param reverse_order: 向更旧的记录翻页时设为 True；默认 False 保持原工具行为。

Input Schema

NameRequiredDescriptionDefault
countNo获取的消息条数，默认 20
group_idYes群号
message_seqNo历史游标，填上一页最早记录的 message_id；NapCat 的参数名沿用 message_seq，但不要填返回记录的 message_seq。不填则取最新记录。
reverse_orderNo向更旧的记录翻页时设为 True；默认 False 保持原工具行为。

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv1.1.0
    • addedInput schema / additionalProperties
      Added value: +false
    • changedInput schema / properties / message_seq / description
      Previous value: -"起始消息序号 (可选，不填则从最新一条往前拉取)"New value: +"历史游标，填上一页最早记录的 message_id；NapCat 的参数名沿用 message_seq，但不要填返回记录的 message_seq。不填则取最新记录。"
    • addedInput schema / properties / reverse_order
      Added value: +{
+  "default": false,
+  "description": "向更旧的记录翻页时设为 True；默认 False 保持原工具行为。",
+  "type": "boolean"
+}
  2. First observedv1.0.0

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It does disclose meaningful behavior: default count of 20, that omitting message_seq returns the newest records, and that reverse_order changes paging direction. It omits read-only/safety framing and any rate-limit or permission context, so it is partial but not misleading.

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?

Front-loads purpose followed by cursor/paging semantics, which is the right order. Slightly padded by restating parameters already documented verbatim in the schema, and the trailing mixed-language sentence about True/False is a bit awkward.

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?

No output schema exists, yet for a read-only history fetch the description covers the essentials an agent needs: group target, page size, cursor semantics, and paging direction. Return shape and message ordering when paging are left unstated, but nothing critical to invoking it correctly is missing.

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 coverage is 100%, so the baseline is 3, but the description actually resolves a genuine trap: message_seq must be the earlier page's message_id, not the returned record's message_seq field. That is real semantic value beyond the schema text for a paging cursor.

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 concrete verb+resource (获取指定群聊的历史聊天记录) and names the backing action (NapCat OneBot 11: get_group_msg_history). Scoping to 群聊 implicitly separates it from get_friend_msg_history, but no sibling is named explicitly.

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?

Implied when-to-use: fetching history of a specific group. It adds useful pagination guidance (reverse_order=True 向更旧的记录翻页, message_seq as cursor, default = latest), which is effectively usage guidance for this tool. However, it never says when to prefer this over get_recent_messages, get_recent_contact, or get_msg.

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