Send Push Notification
send_notificationSend 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
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 |
|---|---|---|---|
| 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 | Default |
|---|---|---|---|
| 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. |