Skip to main content
Glama

notify_master

Sends a Bilibili private message to the master with a video title, link, and reason it is worth watching, while respecting dry-run and daily notification limits.

Instructions

B站 私信通知主人(判 B 的 B站 视频用,附标题 / 链接 / 为什么值得看)。受 actions.dryRun 和 notifyPerDay 约束。

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": {
      "text": "<text>"
    },
    "name": "notify_master"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYes私信内容,建议 200 字内:标题 + 链接 + 理由

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries the full burden and does disclose two real behavioral constraints: actions.dryRun (the message may not actually be delivered) and notifyPerDay (a daily quota). It omits what happens when the quota is exhausted, whether failures are surfaced or silently dropped, and whether login is required — significant gaps for a tool with an external side effect.

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 sentence plus a short constraint clause, front-loaded with purpose and audience, then the payload format, then the limits. No filler or redundant phrasing.

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 notification tool with no output schema and no annotations, the description covers purpose, payload shape, and two operating constraints. It still leaves the agent unsure about the outcome of a call — whether success is confirmed, what error arises on quota exhaustion, and how dryRun affects the visible result.

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 parameter, so the baseline is already met by the schema's own '建议 200 字内:标题 + 链接 + 理由'. The description restates the same content expectations, adding little beyond the schema, but the schema itself is complete, so a 4 is fair rather than a 3.

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?

Names a specific verb and channel (B站 私信通知主人) and scopes it to one workflow (判 B 的 B站 视频用), plus the expected payload (标题 / 链接 / 为什么值得看). It is clearly distinguishable from siblings like check_notification or flush_notifications, though it never names an alternative explicitly.

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?

The parenthetical '(判 B 的 B站 视频用)' implies the triggering context, and the dryRun/notifyPerDay clause hints at gating conditions. However there is no explicit when-not-to-use guidance, no mention of alternatives such as submit_verdict or check_notification, and no statement of prerequisites like being logged in.

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