Skip to main content
Glama

flush_notifications

Sends due Bilibili notification queue entries while skipping items with unknown delivery status to prevent duplicate messages.

Instructions

尝试发送到期的B站通知队列,未知送达状态不会重复发送。

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

B3.4/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It does disclose one important behavior: items with unknown delivery status are not sent again, so there is no duplicate sending. It omits the external side effect of actually delivering messages, whether authentication is required, and any return information.

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?

One short sentence, with the action and the scoping condition stated first and the deduplication guarantee second; there is no filler.

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?

Because the tool has no parameters, no output schema, and no annotations, the description does not need to be long. It covers purpose and deduplication, but says nothing about authentication prerequisites, how results or failures are reported, or whether the call is one-shot or loops through the queue.

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 no parameters, so there is nothing for the description to explain beyond what the schema shows. The baseline for a zero-parameter tool is a 4.

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-plus-resource: attempt to send the due Bilibili notification queue. The scope qualifier "due" separates it from a generic notify call such as notify_master, though no sibling is named explicitly.

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

Usage Guidelines2/5

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

There is no guidance on when to call this tool rather than check_notification or notify_master, and no prerequisite such as login state being mentioned. The word "due" implies it sends only queued items that are due, but when to use it is left entirely to inference.

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