Skip to main content
Glama

mark_msg_as_read

Marks QQ messages as read for the current account, automatically routing group or private chats by a valid message ID to update read status.

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_msg_as_read"
  }
}

Input Schema

NameRequiredDescriptionDefault
target_idNo
message_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already flag this as non-readonly, non-destructive, open-world. The description adds genuinely useful behavioral facts beyond them: negative message_id values are legal, and the target message must exist in the current account's storage or the call presumably fails. However, it does not say what happens on a missing message or what the call returns.

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?

A single dense sentence that front-loads the action and routing behavior before the message_id sourcing rules. No filler, though the punctuation makes it slightly run-on.

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 critical message_id sourcing and validation rules but leaves target_id unexplained and does not address failure modes or return behavior.

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

Parameters2/5

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

Schema description coverage is 0%, so the description carries the full burden. It explains message_id well (source: message events or send results, negatives legal), but the second parameter target_id is never mentioned, leaving its meaning entirely undocumented in both schema and description.

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 ('标记消息已读') and adds the '群聊/私聊自动路由' qualifier, which implicitly distinguishes it from the family of sibling tools that target one chat type. It does not name those siblings, so differentiation is inferred rather than explicit.

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?

The description gives prerequisites (message must be queryable in the current account's message storage) and tells the agent where message_id comes from, but it never says when to prefer this over mark_group_msg_as_read or mark_private_msg_as_read. Usage is implied by the auto-routing note, not stated as an explicit alternative comparison.

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