Skip to main content
Glama
haoan33

OmniQQ-MCP

by haoan33
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

get_friend_msg_history

Fetch historical private chat messages with a specified QQ friend from NapCat, using count, message_seq, and reverse_order to page through recent or older records.

Instructions

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

Input Schema

NameRequiredDescriptionDefault
countNo获取的消息条数，默认 20
user_idYes好友 QQ 号
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

B3.3/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full disclosure burden. It adds real behavioral context around the pagination cursor and the reverse_order flag, but says nothing about permissions, friend-relationship prerequisites, rate limits, or the shape of returned records.

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

Conciseness3/5

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

The purpose is front-loaded in the first clause, which is good. But the four inline :param lines restate the schema descriptions almost verbatim, adding redundancy rather than new information.

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?

For a paginated history tool with no output schema and no annotations, the description covers the cursor mechanics adequately but omits the return structure and any prerequisites, leaving an agent to infer how to interpret the fetched records.

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 100%, so the schema already documents all four parameters, including defaults for count and reverse_order. The description's parameter notes largely duplicate the schema text, adding only the framing that message_seq is not the returned message_id.

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 description states a specific verb and resource: fetching historical private-chat messages with a specified friend from NapCat. The 'friend' (私聊) scope implicitly separates it from the sibling get_group_msg_history, but it never explicitly names or contrasts any alternative, so it stops short of a 5.

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 explains how to paginate (fill message_seq with the oldest message_id from the previous page, set reverse_order=True to go older), which is genuine usage guidance. However, it gives no guidance on when this tool is preferable to siblings like get_recent_messages, get_msg, or get_group_msg_history.

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