Skip to main content
Glama
appricos

mcp-pushinator

by appricos

send-notification

Trigger push notifications to specific devices by sending a channel ID and content via the Pushinator API. Integrate into LLM workflows for real-time alerts.

Instructions

Send a notification via the Pushinator API

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
channel_idYesUUID of the channel to send the notification to
contentYesString content of the notification

Implementation Reference

  • The handler function for the 'send-notification' tool. It makes a POST request to the Pushinator API to send a notification with the given channel_id and content, then returns the response message.
    async ({ channel_id, content }) => {
        const notificationUrl = `${PUSHINATOR_API_BASE}/notifications/send/`;
    
        const response = await fetch(notificationUrl, {
            method: "POST",
            headers: {
                "Content-Type": "application/json",
                "User-Agent": USER_AGENT,
                "Authorization": `Bearer ${process.env.PUSHINATOR_API_KEY}`,
            },
            body: JSON.stringify({
                channel_id,
                content,
            }),
        });
    
    
        const responseData: PushinatorResponse = await response.json();
    
        return {
            content: [
                {
                    type: "text",
                    text: responseData.message,
                },
            ],
        };
    },
  • Zod input schema defining parameters for the 'send-notification' tool: channel_id (string UUID) and content (string).
    {
        channel_id: z.string().describe("UUID of the channel to send the notification to"),
        content: z.string().describe("String content of the notification"),
    },
  • src/index.ts:51-86 (registration)
    Registration of the 'send-notification' tool using server.tool(), specifying name, description, input schema, and handler function.
    server.tool(
        "send-notification",
        "Send a notification via the Pushinator API",
        {
            channel_id: z.string().describe("UUID of the channel to send the notification to"),
            content: z.string().describe("String content of the notification"),
        },
        async ({ channel_id, content }) => {
            const notificationUrl = `${PUSHINATOR_API_BASE}/notifications/send/`;
    
            const response = await fetch(notificationUrl, {
                method: "POST",
                headers: {
                    "Content-Type": "application/json",
                    "User-Agent": USER_AGENT,
                    "Authorization": `Bearer ${process.env.PUSHINATOR_API_KEY}`,
                },
                body: JSON.stringify({
                    channel_id,
                    content,
                }),
            });
    
    
            const responseData: PushinatorResponse = await response.json();
    
            return {
                content: [
                    {
                        type: "text",
                        text: responseData.message,
                    },
                ],
            };
        },
    );
  • TypeScript interface defining the expected response structure from the Pushinator API, used in the tool handler.
    interface PushinatorResponse {
        message: string;
        success: boolean;
    }
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the action is to 'send' a notification, implying a write operation, but fails to mention critical aspects like authentication needs, rate limits, error handling, or what happens after sending (e.g., success confirmation). This leaves significant gaps in understanding the tool's behavior.

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?

The description is a single, efficient sentence that directly states the tool's purpose without any wasted words. It is appropriately sized and front-loaded, making it easy to understand at a glance.

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

Completeness2/5

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

Given the complexity of a notification-sending tool with no annotations and no output schema, the description is insufficient. It lacks details on behavioral traits (e.g., side effects, response format), usage context, and error handling, making it incomplete for effective agent use.

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?

The input schema has 100% description coverage, with clear documentation for both parameters (channel_id as UUID, content as string). The description adds no additional semantic context beyond what the schema provides, such as examples or constraints, so it meets the baseline for high schema coverage.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action ('send') and resource ('notification via the Pushinator API'), providing a specific verb+resource combination. However, with no sibling tools mentioned, it cannot demonstrate differentiation from alternatives, which prevents a perfect score.

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?

The description provides no guidance on when to use this tool, such as prerequisites, typical scenarios, or limitations. It lacks any context about alternatives or exclusions, leaving usage entirely implicit.

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

Related 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/appricos/pushinator-mcp'

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