Bell

by YongyangFu

Overview Schema Source Related Servers Discussions Admin

Python

Local

notify_done

Get a desktop popup notification when a task completes. Send a brief summary to trigger a Bell alert.

Instructions

Show a Bell popup when a task finishes; keep summary short, about 120 characters.

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": {
      "summary": "<summary>"
    },
    "name": "notify_done"
  }
}

Input Schema

Name	Required	Description	Default
`session`	No
`summary`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jul 13, 2026

TDQS

A3.8/5.0

Behavior3/5

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

Describes the output as a Bell popup, but no annotations exist to pre-declare safety or side effects. The description adds the character constraint but lacks details like dismissal behavior, persistence, or whether it blocks. For a simple notification, this is moderately transparent.

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?

Single sentence, front-loaded with action, no waste. Essential information is conveyed efficiently.

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?

Tool is simple, and output schema likely covers return values. However, the description omits session parameter context and does not clarify if any side effects (e.g., persistent notifications) exist. Adequate but not fully complete given no annotations.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, so description must compensate. It explains 'summary' with a character limit but does not define its role (e.g., message text). 'Session' parameter is completely unaddressed, leaving ambiguity. This partially adds meaning but insufficiently for two parameters.

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?

Clearly states the tool shows a Bell popup when a task finishes, with a specific verb ('Show') and resource ('Bell popup'). Distinguishes from any potential sibling by its unique action, though no siblings are listed.

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?

Provides a guideline to keep the summary short (~120 characters), which implies appropriate usage context for concise notifications. No explicit when/when-not guidance, but the tool's purpose is self-evident given no siblings.

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

Deploy Server

Other Tools

notify_doneA