mcp-win-toast
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| show_toastB | Windowsのトースト通知を表示します |
| show_dialogC | Windows標準のOKボタン付きダイアログボックスを表示します |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 2 tools
The two tools serve clearly distinct purposes: show_dialog displays a modal dialog box with an OK button, while show_toast shows a non-modal toast notification. An agent can easily differentiate them based on the behavior.
Both tool names follow the consistent verb_noun pattern (show_dialog, show_toast), making the naming predictable and easy to understand.
With only 2 tools, the server is minimal, but for its specific domain of Windows notification types, the count is reasonable and not excessive. It could benefit from additional dialog variations, but the current scope is justifiable.
The server covers the two most common Windows notification types (dialog and toast). Minor gaps exist, such as the lack of dialogs with custom buttons or toast with actions, but the core functionality is present.