Skip to main content
Glama

标记通知已读

gwl_mark_notifications_read

Mark specified global or personal notifications as read and return updated unread counts; use it to clear unread items for the current user.

Instructions

把指定通知标记为已读,返回新的未读计数 {unread{total,global,personal}}。 global_ids 与 personal_ids 至少要给一个且不能是空列表,否则本工具直接报错。 只能标记自己的通知;别人的 id 会被上游静默忽略。操作幂等(重复调用结果一致)。

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": "gwl_mark_notifications_read"
  }
}

Input Schema

NameRequiredDescriptionDefault
global_idsNo要标记已读的全局通知 id(最多 500 个,超出上游会截断)。
personal_idsNo要标记已读的个人通知 id(最多 500 个,超出上游会截断)。

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior1/5

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

The description asserts '操作幂等(重复调用结果一致)' while the annotations declare idempotentHint=false. That is a direct conflict on exactly the property an agent uses to decide whether retrying is safe, so the description actively misleads on a retry-critical trait. The remaining behavioral content (error on empty ids, silent ignore of foreign ids, return counts) is genuinely useful, but the contradiction is the dominant signal.

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

Conciseness5/5

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

Four compact lines, front-loaded with the action, then the return value, then the hard input constraint, then ownership/idempotency caveats. No filler and no restatement of the title.

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?

Even though an output schema exists, the description still surfaces the return shape, plus the error condition and ownership semantics an agent needs to call it correctly. Only the incorrect idempotency claim keeps it from being fully complete and trustworthy.

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?

Schema coverage is 100%, so per-dimension baseline is 3, but the description adds meaning the schema lacks: the schema marks both arrays nullable with no required list, while the description states at least one must be present, non-empty, or the tool errors. That cross-parameter constraint is real added semantics.

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 names a specific verb+resource (mark the specified notifications as read) and even states the returned payload shape {unread{total,global,personal}}. It doesn't explicitly contrast itself with the listing sibling (gwl_list_notifications), but the mutating intent is unambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives concrete invocation rules that select correct usage: at least one of global_ids/personal_ids must be supplied and non-empty, otherwise the call errors. It also scopes ownership ('only your own notifications; others' ids are silently ignored'). It does not say when to prefer this over another tool, but there is no obvious alternative for this action.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.