Skip to main content
Glama

我的通知

gwl_list_notifications
Read-onlyIdempotent

Retrieve personal notifications, visible global notifications, and unread counts in one call; use the limit parameter (1–200) to cap returned items.

Instructions

返回我的站内通知 + 我当前可见的全局通知 + 未读计数。 结构:{personal[], global[](带 is_read), unread{total,global,personal}}。 这不是分页包络,用 limit 截断(默认 100,最大 200)。

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

Input Schema

NameRequiredDescriptionDefault
limitNo返回条数上限(1~200),默认 100。

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is covered. The description adds genuinely new behavioral facts: there is no pagination envelope, so results cannot be paged through beyond limit, and limit acts as a hard truncation cap (default 100, max 200). That is exactly the kind of caveat annotations cannot express.

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?

Three compact lines: what is returned, the exact response shape, then the truncation caveat. Front-loaded and free of filler; the only minor overlap is restating the limit default and maximum already in the schema.

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?

An output schema exists and annotations cover the safety profile, so the description need not explain return values — yet it does anyway, which helps set expectations before the call at slight redundancy cost. What is missing is ordering/freshness of results and whether unread-only filtering is possible, minor for a zero-required-param read.

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% for the single limit parameter, so the baseline would be 3. The description earns an extra point by reframing limit as a truncation cap rather than a page size ('这不是分页包络'), which changes how the agent should interpret and size it.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource (list my notifications) and precisely enumerates the three components returned: personal notifications, global notifications visible to me with is_read, and unread counts. The composite nature of the resource is fully disambiguated, so an agent knows exactly what it gets without opening the schema.

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 is only implied — check my notifications — with no explicit when-to-use versus alternatives such as gwl_mark_notifications_read, and no guidance on when to fetch notifications at all. It does give operational guidance on the limit parameter (truncation rather than paging), which is worth some credit.

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