Skip to main content
Glama

mark_all_as_read

Marks all conversations on the current QQ account as read, clearing unread message indicators in one action.

Instructions

标记全部已读 会将当前账号的会话标记为已读。

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "mark_all_as_read"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false and openWorldHint=true, so the safety profile is largely covered. The description adds the useful scope disclosure that the operation applies to the entire current account with no filtering possible, but says nothing about whether already-read items are touched, whether the action is reversible, or what the response contains.

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?

One short sentence with no padding, and the scope ('全部', '当前账号') is front-loaded. Minor waste comes from the leading phrase restating the tool name before the explanatory clause.

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?

For a parameterless, output-schema-less bulk action, the description covers the essential facts: what changes and how broadly it applies. The remaining ambiguity — whether all conversations or only unread ones are affected, and whether the change is reversible — is minor but would matter for an irreversible-looking write.

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?

The tool takes zero parameters, so the baseline is 4 and there are no parameter semantics the description needs to carry. It correctly conveys that the action is unconditional rather than accepting filters, which is the only parameter-adjacent fact available.

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 ('标记全部已读' / marks conversations as read) and quantifies the scope as all conversations of the current account, which implicitly separates it from the per-message siblings (mark_msg_as_read, mark_private_msg_as_read, mark_group_msg_as_read). It stops short of naming or explicitly contrasting those alternatives.

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?

Bulk-clear intent is implied by '全部' (all) and by the complete absence of parameters, so an agent can infer this is the account-wide cleanup action. There is no explicit when-to-use/when-not-to-use statement, no prerequisite that unread items exist, and no pointer to the narrower per-message alternatives.

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