Skip to main content
Glama

Turbo Notify: WhatsApp for AI agents

Get a message's delivery status

get_message_status
Read-onlyIdempotent

Check where a WhatsApp message got to: queued, sent, delivered, read, failed.

Status only moves forward. A failed status always carries an error code, and for a few media and reaction problems it also carries a hint naming the field to change; most failures give the code alone. Read the code before retrying, because most failures repeat identically.

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": {
      "message_id": "<message_id>"
    },
    "name": "get_message_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
message_idYesMessage id (`msg_…`), as returned by a send or by `list_messages`.
number_aliasNoWhich of the organization's WhatsApp numbers this acts on: `main`, the alias of an extra number, or the number's `id` (`num_…`), which stays the same when the alias is renamed. Call `list_numbers` to see them. Defaults to the main number.main

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior5/5

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

Beyond the annotations (readOnly, idempotent, openWorld), the description discloses real behavioral traits: status is monotonic ('only moves forward'), failed statuses always carry an error code, some media/reaction failures include a hint naming the field to change, and most failures repeat identically so blind retries are wasteful. That is exactly the kind of context an agent cannot get from annotations or schema.

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 status enumeration is front-loaded in the first sentence, followed by two short paragraphs on state progression and failure codes. Every sentence carries information an agent would otherwise have to discover empirically; there is no filler.

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 two-parameter read-only lookup with an output schema, annotations, and full schema coverage, nothing essential is missing. The description supplies the failure-mode and retry semantics that the structured fields cannot express, and correctly omits return-value documentation that the output schema already covers.

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%, with both message_id (msg_… format) and number_alias (main vs alias vs num_… id, list_numbers pointer) fully documented in the schema. The description adds no parameter-level meaning, which is acceptable given the schema already carries it, but earns only baseline credit.

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?

States a specific verb and resource ('Check where a WhatsApp message got to') and enumerates the exact status values returned (queued, sent, delivered, read, failed), so the agent knows precisely what this returns. It does not explicitly contrast itself with the near-neighbor get_message_receipts, leaving a small differentiation gap.

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 rather than stated: the agent infers this is called after a send or a list_messages lookup to poll delivery. The 'read the code before retrying' sentence is post-call guidance on handling failures, not when-to-use-this-vs-alternatives guidance, and no sibling is named as an alternative.

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.