Skip to main content
Glama

mark_private_msg_as_read

Marks a QQ private chat message as read using its real message_id, so the account's unread state stays accurate after handling or responding to a direct message.

Instructions

标记私聊消息已读 使用消息事件或发送结果中的真实 message_id,负值合法;消息须在当前账号的消息存储中可查询。

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": {
      "message_id": "<message_id>"
    },
    "name": "mark_private_msg_as_read"
  }
}

Input Schema

NameRequiredDescriptionDefault
user_idNo
message_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, openWorldHint=true, so the write-but-not-destructive profile is known. The description adds genuinely new constraints (id must be resolvable in the account's message store, negative ids accepted), but says nothing about failure behavior, permissions, or what state changes on success.

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?

Purpose is front-loaded in the first clause, followed by two compact semicolon-delimited constraints. No filler, though the run-on single line is slightly harder to scan than separated sentences.

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 two-parameter mutation with no output schema, the definition covers the tricky id semantics well but leaves user_id undocumented and omits any statement of the return or error outcome. Adequate but with a clear coverage hole.

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 0%, so the description must compensate and only partly does. It clarifies message_id (real id from events/send results, negatives allowed), which explains why the schema forbids only 0, but the user_id parameter is never mentioned in either place.

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 and resource: marking a private-chat message as read. The qualifier 私聊 implicitly separates it from mark_group_msg_as_read and mark_all_as_read without naming them, so an agent can route correctly, though 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?

Gives actionable provenance guidance: take the real message_id from a message event or a send result, and the message must exist in the current account's store. It stops short of stating when to prefer mark_group_msg_as_read or mark_all_as_read instead, or what to do when the message is not found.

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