Skip to main content
Glama

mark_group_msg_as_read

Marks a specified group message as read by its real message_id, using IDs from message events or send results.

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

Input Schema

NameRequiredDescriptionDefault
group_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 a non-read-only, non-destructive, open-world mutation, and the description does not contradict them. It adds useful preconditions beyond the annotations (message_id must come from real message events or send results, and the message must be queryable in the current account's storage), but says nothing about failure behavior 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?

A single front-loaded sentence states the action first, then the constraints, separated by semicolons. Dense but every clause carries information; only the phrasing is slightly cramped.

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 simple two-parameter tool with annotations and no output schema, the description is close to sufficient, but the complete silence on group_id leaves a real hole in an otherwise small surface. An agent cannot tell whether group_id is required for group context or merely optional metadata.

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. It does well for message_id (source of the value, negative values are valid, must be resolvable in storage), but group_id is never mentioned, leaving one of two parameters entirely unexplained 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?

The description gives a specific verb+resource (mark group messages as read), and the 'group' qualifier implicitly separates it from siblings like mark_private_msg_as_read and mark_all_as_read. It stops short of naming those alternatives explicitly, so an agent must infer the routing rule from the scope word alone.

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?

Usage context is only implied by the '群消息' scope and by the precondition that the message must exist in the current account's storage. There is no explicit when-to-use / when-not-to-use statement and no named alternative for private or bulk marking.

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