Skip to main content
Glama

check_notification

Verify unknown notification delivery status by matching the sending account, message body, and timestamp against Bilibili chat history; keep the original status when no match is confirmed.

Instructions

通过B站聊天历史核实送达状态未知的通知,匹配发送账号、正文和时间;未确认时保留原状态。

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": {
      "operation_id": "<operation_id>"
    },
    "name": "check_notification"
  }
}

Input Schema

NameRequiredDescriptionDefault
operation_idYesget_audit.queue 中的 key

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A3.5/5.0
Behavior3/5

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

No annotations exist, so the description carries the full behavioral burden. It usefully discloses the matching criteria and the fallback rule (retain original status when unconfirmed), but leaves the consequences when confirmation succeeds unstated, and says nothing about auth requirements, external calls to Bilibili chat history, or side effects on the audit record.

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 dense sentence with the action, the target, the mechanism, and the fallback behavior front-loaded in that order. Nothing is redundant or padding.

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 one-parameter tool with no annotations and no output schema, the description should say what the caller gets back (per-notification result? counts? updated status?) and what happens on success. It covers the matching and the unconfirmed path but leaves the return contract and success-path effects unspecified.

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?

There is a single parameter whose schema description is fully covered (100%), including where the key comes from (get_audit.queue). The description adds no meaning beyond that — it never references operation_id, the queue, or the key format — so the baseline 3 applies.

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 (核实 / verify) and a specific resource (notifications whose delivery status is unknown), plus the mechanism (Bilibili chat history) and the matching keys (sending account, body text, time). This lets an agent distinguish it from sibling tools such as flush_notifications or get_audit, although it never names an alternative outright.

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 implied by the qualifier '送达状态未知的通知' (notifications with unknown delivery status), which tells the agent the triggering condition. However, there is no explicit when-not guidance, no mention of the related get_audit or flush_notifications siblings, and no statement of prerequisites (e.g., login state) needed before calling.

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