push-notification-mcp

by TG-Techie

Overview Schema Source Related Servers Discussions Admin

JavaScript

Local

Send Notification

send_notification

Send a push notification to alert the user when a task completes, input is needed, or attention is required.

Instructions

Send a push notification to the user. Use this to alert the user when a long-running task completes, when input is needed, or when something requires their attention.

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": {
      "title": "<title>",
      "body": "<body>"
    },
    "name": "send_notification"
  }
}

Input Schema

Name	Required	Description	Default
`body`	Yes	Notification body text. Describes what happened or what the user needs to know.
`title`	Yes	Short notification title. Typically identifies the context: branch name, workspace name, project name, or repository name.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jul 6, 2026

TDQS

A4.2/5.0

Behavior3/5

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

Annotations are all false, so description carries full burden. It states 'send' but does not disclose potential side effects (e.g., rate limits, user opt-in, delivery guarantees). Basic behavior is clear but lacks depth.

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?

Two sentences, front-loaded with the action. Every sentence adds value with no wasted words.

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

Completeness4/5

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

For a simple notification tool with no output schema and no siblings, the description covers purpose and usage well. Minor lack of detail on return behavior, but acceptable.

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 covers 100% with detailed descriptions for each parameter. The description reinforces overall context but does not add new parameter-level details beyond what the schema provides.

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 the action ('Send a push notification') and provides specific use cases (long-running task completion, input needed, attention required), making the purpose highly distinct.

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

Usage Guidelines5/5

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

Explicit guidance is given on when to use: 'when a long-running task completes, when input is needed, or when something requires their attention.' No alternatives exist, so no exclusion needed.

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

send_notificationA