Pushary

Send Push Notification

send_notification

Destructive

Send a notification to connected devices for a requested update or a meaningful unattended result, such as a finished task. Delivery follows the account policy and optional recipient filters. context adds a detail page. context.askQuestion is kept for older clients; ask questions with ask_user. Returns web/mobile delivery counts and a warning when no delivery channel is connected. Sends real notifications. API reference: https://pushary.com/docs/agents/reference/tools#send_notification

Input Schema

Name	Required	Description
`env`	No	Set to "test" from a test suite. The notification is recorded in the activity feed and nothing is delivered to a phone or browser. The X-Pushary-Env: test header does the same for every call on the connection.
`url`	No	URL opened when the user taps the notification. Ignored if context is provided, because a context detail page URL is generated automatically.
`body`	Yes	Notification body text (max 500 chars). One or two sentences the user can act on without opening anything.
`tags`	No	Deliver only to subscribers that have any of these tags.
`title`	Yes	Notification title shown on the lock screen (max 100 chars). Lead with the outcome, e.g. "Build finished" or "Migration failed".
`context`	No	Structured context rendered as a rich detail page when the user taps the notification. Strongly recommended for task_complete and error notifications so the user can act from their phone.
`iconUrl`	No	URL of the notification icon image
`imageUrl`	No	URL of a large image shown in the notification
`agentName`	No	Name of the agent sending this notification, format "{Agent} - {project}" (e.g. "Claude Code - myproject"). Shown in the notification so the user knows which session is talking. Falls back to the MCP client name if omitted.
`machineId`	No	Stable machine id of the sending agent, so two machines never collapse into one session.
`sessionId`	No	Opaque per-session id of the sending agent, so parallel sessions are attributed separately in the activity feed.
`externalIds`	No	Deliver only to subscribers matching these external IDs.
`subscriberIds`	No	Deliver only to these subscriber IDs. Omit all targeting fields to reach every connected device.

Output Schema

Name	Required	Description
`env`	No	Echoed when the call was test traffic.
`hint`	No	What to do next, when there is a next step.
`sent`	No	Total devices reached, web plus mobile. Zero is a successful call that found nobody to deliver to, not an error.
`status`	No	Outcome when a session completion is recorded for delivery once per turn.
`updates`	No	Effective update delivery setting and the policy that selected it.
`warning`	No	Present only when the notification reached zero devices, naming what the user has to connect.
`delivery`	No	Per-channel outcome. The two channels are independent with no cross-fallback, so each reports its own result.
`suppressed`	No	Reason the notification was recorded without a push.
`attribution`	No	Whether real session and machine identifiers were supplied. Unattributed notifications are delivered without creating a live session.
`completionId`	No	Recorded completion identifier, or null when no completion was recorded.
`notificationId`	No	Trace ID for this notification; provider acceptance does not confirm a person saw it.
`linkedCorrelationId`	No	Present only when context.askQuestion embedded a decision prompt. Pass it to wait_for_answer to collect the response.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 24, 2026

changedInput schema / properties / context / properties / askQuestion / description

Previous value: -"Embed a decision prompt on the detail page. The response includes a linkedCorrelationId; pass it to wait_for_answer to collect the answer. The embedded question expires 10 minutes after it is created. Only for a decision about unfinished work. Not for asking what to do next once the requested work is complete, unless the user asked you to."New value: +"Kept for older clients. To ask the user something, call ask_user instead: it stays open at least as long, offers lock-screen answers on confirm questions, and, unless the agent connects through a connector, stays open until answered or cancelled. An embedded question appears on the detail page, closes 10 minutes after it is created, and returns a linkedCorrelationId for wait_for_answer. Only for a decision about unfinished work. Not for asking what to do next once the requested work is complete, unless the user asked you to."

Changed4 schema fields changedOct 23, 2026

addedOutput schema / properties / completionId

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "description": "Recorded completion identifier, or null when no completion was recorded."
+}

addedOutput schema / properties / status

Added value: +{
+  "description": "Outcome when a session completion is recorded for delivery once per turn.",
+  "enum": [
+    "recorded",
+    "ignored"
+  ],
+  "type": "string"
+}

addedOutput schema / properties / suppressed

Added value: +{
+  "description": "Reason the notification was recorded without a push.",
+  "type": "string"
+}

addedOutput schema / properties / updates

Added value: +{
+  "additionalProperties": false,
+  "description": "Effective update delivery setting and the policy that selected it.",
+  "properties": {
+    "mode": {
+      "enum": [
+        "both",
+        "phone",
+        "browser",
+        "none"
+      ],
+      "type": "string"
+    },
+    "source": {
+      "enum": [
+        "kill",
+        "snooze",
+        "setting",
+        "mode",
+        "default"
+      ],
+      "type": "string"
+    }
+  },
+  "required": [
+    "mode",
+    "source"
+  ],
+  "type": "object"
+}

Changed1 schema field changedOct 18, 2026

changedInput schema / properties / context / properties / askQuestion / description

Previous value: -"Embed a decision prompt on the detail page. The response includes a linkedCorrelationId; pass it to wait_for_answer to collect the answer. The embedded question expires 10 minutes after it is created."New value: +"Embed a decision prompt on the detail page. The response includes a linkedCorrelationId; pass it to wait_for_answer to collect the answer. The embedded question expires 10 minutes after it is created. Only for a decision about unfinished work. Not for asking what to do next once the requested work is complete, unless the user asked you to."

Changed1 schema field changedOct 7, 2026

addedOutput schema / properties / notificationId

Added value: +{
+  "description": "Trace ID for this notification; provider acceptance does not confirm a person saw it.",
+  "format": "uuid",
+  "pattern": "^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$",
+  "type": "string"
+}

Changed2 schema fields changedOct 7, 2026

changedInput schema / properties / context / properties / type / description

Previous value: -"What kind of update this is. Use \"task_complete\" when work finished, \"error\" when something failed (delivered with high urgency), \"info\" for everything else."New value: +"What kind of update this is. Use \"task_complete\" when work finished, \"error\" when something failed (delivered with high urgency), \"info\" for everything else. Error severity describes this notification, not the agent session health."

addedOutput schema / properties / attribution

Added value: +{
+  "description": "Whether real session and machine identifiers were supplied. Unattributed notifications are delivered without creating a live session.",
+  "enum": [
+    "session",
+    "unattributed"
+  ],
+  "type": "string"
+}

Changed1 schema field changedOct 6, 2026
- changedInput schema / properties / context / properties / askQuestion / properties / question / maxLength
```
Previous value: -500New value: +8000
```

Changed2 schema fields changedSep 2, 2026

addedInput schema / properties / env

Added value: +{
+  "description": "Set to \"test\" from a test suite. The notification is recorded in the activity feed and nothing is delivered to a phone or browser. The X-Pushary-Env: test header does the same for every call on the connection.",
+  "enum": [
+    "test"
+  ],
+  "type": "string"
+}

addedOutput schema / properties / env

Added value: +{
+  "description": "Echoed when the call was test traffic.",
+  "enum": [
+    "test"
+  ],
+  "type": "string"
+}

Changed1 schema field changedAug 17, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "delivery": {
+      "additionalProperties": false,
+      "description": "Per-channel outcome. The two channels are independent with no cross-fallback, so each reports its own result.",
+      "properties": {
+        "mobile": {
+          "additionalProperties": false,
+          "properties": {
+            "recipients": {
+              "description": "Phones that accepted the push.",
+              "type": "number"
+            },
+            "status": {
+              "description": "Why mobile delivery reached nobody, present only when it reached nobody.",
+              "type": "string"
+            }
+          },
+          "required": [
+            "recipients"
+          ],
+          "type": "object"
+        },
+        "web": {
+          "additionalProperties": false,
+          "properties": {
+            "recipients": {
+              "description": "Browsers that accepted the push.",
+              "type": "number"
+            },
+            "status": {
+              "description": "Why web delivery reached nobody, present only when it reached nobody.",
+              "type": "string"
+            }
+          },
+          "required": [
+            "recipients"
+          ],
+          "type": "object"
+        }
+      },
+      "required": [
+        "web",
+        "mobile"
+      ],
+      "type": "object"
+    },
+    "hint": {
+      "description": "What to do next, when there is a next step.",
+      "type": "string"
+    },
+    "linkedCorrelationId": {
+      "description": "Present only when context.askQuestion embedded a decision prompt. Pass it to wait_for_answer to collect the response.",
+      "type": "string"
+    },
+    "sent": {
+      "description": "Total devices reached, web plus mobile. Zero is a successful call that found nobody to deliver to, not an error.",
+      "type": "number"
+    },
+    "warning": {
+      "description": "Present only when the notification reached zero devices, naming what the user has to connect.",
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

First observedJul 29, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations declare destructiveHint=true and openWorldHint=true; the description supplies the missing context that 'destructive' here means sending real user-visible notifications rather than data loss. It also discloses delivery-policy behavior, the 'no delivery channel connected' warning, and return values (web/mobile counts), which is real information beyond the annotations.

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?

Purpose and trigger conditions come first, followed by behavior and return values, then the API reference. It is a bit listy and the standalone 'Sends real notifications.' sentence is terse, but every sentence carries information an agent needs.

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?

For a 13-parameter tool with a nested context object, a deprecation trap, and a real-world side effect, the description covers purpose, side effects, delivery semantics, return shape, and the sibling alternative. The output schema and rich parameter descriptions handle the rest.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3; the description still adds value by explaining that context renders a detail page and by giving migration guidance on the deprecated askQuestion field. It does not restate the length limits or targeting fields, deferring correctly to the schema.

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?

States a specific verb and resource ('Send a notification to connected devices') plus the legitimate triggering conditions ('a requested update or a meaningful unattended result, such as a finished task'). It also draws the boundary against the ask_user sibling, so an agent can distinguish it without opening schemas.

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?

Gives clear use conditions (requested update, finished task) and routes question-asking to ask_user rather than the deprecated context.askQuestion path. It stops short of an explicit 'do not use for X' exclusion list, but the alternative is named with its scope.

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

All Pushary tools Inspect

Try in Browser

Context Every Agent Can ShareAgents share what they learn, hand off work, and keep it when you switch models. Start with 5 GB free.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?