Skip to main content
Glama

send_push_notification

Destructive

Sends push notifications to ServiceNow mobile app users (Now Mobile/Mobile Agent) by firing a push-only event, with targeting by user, group, record, and optional action link.

Instructions

Send a push notification to ServiceNow mobile app users (Now Mobile / Mobile Agent) the way ServiceNow does it: an event fires a push-only notification whose push message carries the text. The first call per table sets up, and later calls reuse, an event "nowaikit.push", a push message "NowAIKit push ()" and a notification "NowAIKit push ()". Only users signed in to the mobile app with push enabled receive it; the result says how many recipients have a registered device. [Write]

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_push_notification"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyYesNotification body text
userNoTarget user sys_id or user_name
groupNoTarget group sys_id or name (its active members receive it)
tableNoTable of the record the notification is about (tapping opens it in the app). Default: sys_user, the first recipient
titleYesNotification title (first line of the message)
usersNoMore target users (sys_id or user_name)
groupsNoMore target groups (sys_id or name)
push_appNoPush application (sys_push_application) name or sys_id. Default SkyNowPushApp (Now Mobile / Mobile Agent); SkyNowRequestPushApp for Now Mobile request app
action_urlNoLink appended to the message
setup_onlyNoCreate or check the event, push message and notification without sending anything
record_sys_idNosys_id of that record (required with table)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed10 schema fields changedv5.0.1
    • changedInput schema / properties / action_url / description
      Previous value: -"Deep link URL on tap"New value: +"Link appended to the message"
    • changedInput schema / properties / group / description
      Previous value: -"Target group sys_id (alternative to user)"New value: +"Target group sys_id or name (its active members receive it)"
    • addedInput schema / properties / groups
      Added value: +{
      +  "description": "More target groups (sys_id or name)",
      +  "items": {
      +    "type": "string"
      +  },
      +  "type": "array"
      +}
    • addedInput schema / properties / push_app
      Added value: +{
      +  "description": "Push application (sys_push_application) name or sys_id. Default SkyNowPushApp (Now Mobile / Mobile Agent); SkyNowRequestPushApp for Now Mobile request app",
      +  "type": "string"
      +}
    • addedInput schema / properties / record_sys_id
      Added value: +{
      +  "description": "sys_id of that record (required with table)",
      +  "type": "string"
      +}
    • addedInput schema / properties / setup_only
      Added value: +{
      +  "description": "Create or check the event, push message and notification without sending anything",
      +  "type": "boolean"
      +}
    • addedInput schema / properties / table
      Added value: +{
      +  "description": "Table of the record the notification is about (tapping opens it in the app). Default: sys_user, the first recipient",
      +  "type": "string"
      +}
    • changedInput schema / properties / title / description
      Previous value: -"Notification title"New value: +"Notification title (first line of the message)"
    • changedInput schema / properties / user / description
      Previous value: -"Target user sys_id"New value: +"Target user sys_id or user_name"
    • addedInput schema / properties / users
      Added value: +{
      +  "description": "More target users (sys_id or user_name)",
      +  "items": {
      +    "type": "string"
      +  },
      +  "type": "array"
      +}
  2. First observedv1.0.2

TDQS

A3.9/5.0
Behavior4/5

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

The annotations already declare the safety profile (destructiveHint=true, openWorldHint=true, not idempotent), and the description adds real context beyond them: the first call creates three backing records (event "nowaikit.push", a push message, a notification) that later calls reuse, so the agent understands persistent side effects rather than just a send. It also discloses the delivery constraint (only signed-in users with push enabled) and that the result reports how many recipients have a registered device. It stops short of stating required roles/permissions or that a sent notification cannot be recalled.

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?

Three sentences, front-loaded with the action and audience, then setup/reuse semantics, then delivery constraints and return information. The internal record names ("nowaikit.push", "NowAIKit push (<push app>)") are verbose but earn their place as transparency about what gets created; the "[Write]" tag is a bit redundant against the annotations.

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 an 11-parameter mutating tool with no output schema, the definition covers the non-obvious parts: one-time setup that is reused, who can actually receive the push, and that the response carries a recipient count. The main remaining gap is operational context such as required roles or what happens on a repeat send to the same table.

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 description coverage is 100% and every parameter is documented inline, including defaults for table and push_app and the table/record_sys_id pairing, so the description adds little beyond it. The mention that the push message carries the text and that tapping opens the record lightly reinforces intent but does not introduce new syntax or format guidance.

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 names a specific verb and resource ("Send a push notification to ServiceNow mobile app users") and pins the exact channel (Now Mobile / Mobile Agent push), which separates it from generic notification tools like create_notification or the emergency-broadcast sibling. It also states the underlying mechanism (an event fires a push-only notification whose push message carries the text), so an agent knows precisely what this does before opening the schema.

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

Usage Guidelines3/5

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

Usage is implied through the targeting mechanics (user/group/table, first call sets up, later calls reuse) and the delivery precondition (recipients must be signed in with push enabled), but there is no explicit statement of when to choose this over send_emergency_broadcast, create_notification, or schedule_notification, and no when-not-to-use guidance.

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