Skip to main content
Glama
taylor224

bell-mcp

by taylor224
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
BELL_DEFAULT_SOUNDNoThe default sound to use for bell (beep, ding, ding-ding, warning). Falls back to ding if unset or invalid.ding

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
ring_bellA

Ring a bell through the speakers to alert the human.

Call this when a task is complete or when you need the human's attention.

Args:
    sound: Which bell to ring. One of:
        - "beep"      (Retro Beep): harsh 90s PC-speaker beep
        - "ding"      (Ding): single soft bell tone
        - "ding-ding" (Double Ding): two bell tones in a row
        - "warning"   (Warning Alarm): urgent alternating two-tone alarm
        If omitted, the preset default (BELL_DEFAULT_SOUND, else "ding")
        is used.
    message: Optional note about why the bell is ringing (e.g. "build
        finished", "need your input"). Returned in the confirmation.
list_bellsA

List the available bell sounds (id, name, description) and the default.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

A4.3/5.0

Scored across 2 tools

Disambiguation5/5

Each tool has a clearly distinct purpose: list_bells retrieves available sounds, ring_bell triggers an alert. There is no overlap or ambiguity.

Naming Consistency5/5

Both tools follow a consistent verb_noun pattern ('list_bells', 'ring_bell'), making their actions predictable.

Tool Count5/5

Two tools perfectly match the narrow domain of bell ringing—listing options and ringing—without unnecessary extras.

Completeness5/5

The tool set covers the full lifecycle: discover available sounds and trigger an alert. No missing operations for this focused purpose.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources