Skip to main content
Glama
timtoday

mcp-windows-notify

by timtoday

send_urgent_notification

Send persistent Windows notifications that stay on screen until dismissed, with customizable title, icon, and sound for urgent alerts or reminders.

Instructions

发送醒目的常驻通知(直到用户关闭)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
messageYes通知消息内容
titleNo通知标题(可选)
iconNo通知图标类型(可选)
soundNo是否播放声音(可选)
Behavior3/5

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

The description discloses the persistent, prominent nature and that the user must close it. No annotations exist, so the description carries the burden. It does not mention permission requirements, response behavior, or effects on other notifications.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single concise sentence with no extraneous words. It front-loads the key behavior. Slightly more structure could improve readability, but it is efficient for its length.

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?

Given the tool's simplicity and available sibling tools, the description provides adequate context for an agent to understand the core function. However, adding usage guidance and behavioral details would improve completeness.

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?

Schema description coverage is 100%, so the baseline is 3. The description does not add extra information about the parameters beyond what is in the schema. No parameter-specific elaboration is provided.

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?

The description clearly states it sends a prominent persistent notification that only closes when the user dismisses it. This distinguishes it from siblings like send_notification, which likely sends a non-persistent notification.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance is provided on when to use this tool versus alternatives like notify_ai_work_complete or notify_error. The description implies urgency but does not specify contexts or exclusions.

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/timtoday/mcp-windows-notify'

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