Skip to main content
Glama

notify

Send a WhatsApp notification to the account owner's own phone.

    `text` is the message (1-1024 chars). `image_url` (optional) is a public https
    image link — a screenshot, chart or diff — delivered as an image with `text` as
    the caption when the user's 24h window is open (otherwise text only). Returns a
    confirmation with the queued message id; raises an actionable error on quota/auth.
    `to` (optional): "me" (default), "team" (the owner plus every active team member)
    or a list of team member names or ids (and "me"); one message per recipient.
    `ack` (optional): an "On it" button on each copy inside the 24h window; to a team
    the first tap wins and the others are told who took it (read it via
    `check_replies`).
    `escalate` (optional, with `ack`): while nobody taps, send on to the next people:
    up to 3 steps {"to": "team" or [member names/ids], "after_s": seconds after the
    send, >= 60, each >= 60 after the previous}, or a policy name (POST
    /v1/team/policies). The first tap stops it.
    `actions` (optional): buttons under the alert, up to 3: an action id (one of the
    number's actions), "ack" (the "On it" button, instead of `ack`), "snooze" (mutes
    `topic` for 1h) or {"snooze": minutes}. A tap runs the action with `ref` as its
    context. `topic` (optional): what the alert is about (letters, digits, . _ : / -),
    needed by a snooze; while snoozed, sends with it are suppressed. `ref` (optional):
    your own string (an incident id), sent back with an action's run.
    

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": {
      "text": "<text>"
    },
    "name": "notify"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNome
ackNo
refNo
textYes
topicNo
actionsNo
escalateNo
image_urlNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changed
    • addedInput schema / properties / ack
      Added value: +{
      +  "default": false,
      +  "title": "Ack",
      +  "type": "boolean"
      +}
    • addedInput schema / properties / actions
      Added value: +{
      +  "anyOf": [
      +    {
      +      "items": {
      +        "anyOf": [
      +          {
      +            "type": "string"
      +          },
      +          {
      +            "additionalProperties": true,
      +            "type": "object"
      +          }
      +        ]
      +      },
      +      "type": "array"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "title": "Actions"
      +}
    • addedInput schema / properties / escalate
      Added value: +{
      +  "anyOf": [
      +    {
      +      "items": {
      +        "additionalProperties": true,
      +        "type": "object"
      +      },
      +      "type": "array"
      +    },
      +    {
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "title": "Escalate"
      +}
    • addedInput schema / properties / ref
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "title": "Ref"
      +}
    • addedInput schema / properties / to
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "string"
      +    },
      +    {
      +      "items": {
      +        "type": "string"
      +      },
      +      "type": "array"
      +    }
      +  ],
      +  "default": "me",
      +  "title": "To"
      +}
    • addedInput schema / properties / topic
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "title": "Topic"
      +}
  2. First observed

TDQS

A4.4/5.0
Behavior5/5

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

With zero annotations, the description carries the full burden and does so well: it discloses that the call returns a confirmation with a queued message id, raises actionable errors on quota/auth, sends one message per recipient for team targets, applies first-tap-wins semantics with escalation stopping on the first tap, and suppresses sends to snoozed topics.

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 is front-loaded and each subsequent sentence covers one parameter without filler, so the density is earned. The prose is still paragraph-form and run-on in places, where per-parameter bullets would scan faster for an agent skimming 8 options.

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 tool with 8 interacting options, no annotations, and 0% schema coverage, the description is remarkably complete; an output schema exists so return-shape detail is a bonus rather than required. Minor gaps remain, such as whether `escalate` without a team target degrades gracefully and any rate/volume limits.

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

Parameters5/5

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

Schema coverage is 0% across 8 parameters, so the description must compensate entirely, and it does: it gives text's 1-1024 char bound, requires a public https image link, enumerates `to` values ("me", "team", member names/ids), explains `ack` as a button, details `escalate` step syntax (>= 60s, up to 3 steps, or a policy name), lists allowed `actions` (up to 3, action id, "ack", "snooze", {"snooze": minutes}), plus `topic` charset and `ref` round-trip.

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 opens with a specific verb and resource — "Send a WhatsApp notification to the account owner's own phone" — which is unmistakable. It points to `check_replies` for reading responses, but never contrasts itself with siblings like `ask` or `schedule`, leaving the boundary only implied.

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?

Rich conditional guidance: images arrive as captioned images only when the 24h window is open, `escalate` requires `ack`, `snooze` requires `topic`, and suppression applies while a topic is snoozed. What's missing is explicit routing guidance on when to choose this over `ask`/`schedule` rather than send immediately.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.