Skip to main content
Glama
ekomac

mcp-os-notifications

by ekomac
OverviewSchemaRelated ServersScoreDiscussions
Python

dispatch_os_notification

Send a native OS notification when a task finishes. Customize title, message, urgency, sound, timeout, and optionally notify mobile devices.

Instructions

Dispatch a native OS notification.

Use this tool whenever the user asks to be notified, for example:

  • "notify me when done"

  • "ping me when finished"

  • "let me know when you're done"

  • "send me a notification when complete"

Args: title: Short title for the notification (e.g. "Task finished"). message: Body text explaining what happened (e.g. "Your download is ready"). urgency: Notification priority: "low", "normal" (default), or "critical". sound: Whether to play an audible alert alongside the notification. timeout: Number of seconds before the notification auto-dismisses. -1 means use the OS default. token: Optional stable identifier for this notification. Reusing the same token replaces the previous notification instead of creating a new one. mobile: Also send to configured mobile backends (ntfy.sh, Telegram, Pushover).

Returns: A dictionary with the scheduled notification id, success flag, and details of any mobile dispatch attempts.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
soundNo
titleYes
tokenNo
mobileNo
messageYes
timeoutNo
urgencyNonormal

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Tool Definition Quality

A4.6/5.0
Behavior4/5

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

No annotations provided, so description carries full burden. Explains behavior: token replacement, mobile dispatch, return value. Could mention permission needs, but overall adequate.

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?

Well-structured with intro, usage examples, Args bullet list, and Returns. No fluff; every sentence adds value.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given 7 params (2 required), no annotations, and presence of output schema, the description covers parameters, return value, and use cases comprehensively.

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

Parameters5/5

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

Schema description coverage is 0%, but the description includes a detailed Args section explaining each parameter (title, message, urgency, sound, timeout, token, mobile) with context and defaults, fully compensating.

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?

Starts with 'Dispatch a native OS notification' – a specific verb and resource. Clearly distinguishes from sibling 'notify_user' by providing usage examples for OS notifications.

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?

Explicitly states when to use: 'whenever the user asks to be notified' with concrete examples. Does not explicitly mention when not to use, but the context is clear.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/ekomac/mcp-os-notifications'

If you have feedback or need assistance with the MCP directory API, please join our Discord server