Skip to main content
Glama

WhatsApp message status

whatsapp_message_status
Read-onlyIdempotent

Look up the delivery status of a sent WhatsApp message by its id.

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": {
      "messageId": "<messageId>"
    },
    "name": "whatsapp_message_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
messageIdYesLocal message id

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered elsewhere. The description adds that the target must be a previously sent message and that lookup is by id, but says nothing about behavior for unknown/expired ids, whether status is eventually consistent, or what the status values mean.

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?

One short sentence with the resource and lookup key front-loaded and zero filler. Nothing can be removed without losing information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a single-parameter read tool with full annotation coverage this is close to sufficient, but with no output schema the description is the only place that could say what a status response looks like (e.g., queued/sent/delivered/read/failed). That omission leaves an agent guessing about return values.

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 the single parameter is documented as "Local message id". The description restates the lookup key ("by its id") without adding format, provenance, or scope detail beyond the schema, so the baseline 3 applies.

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?

"Look up the delivery status of a sent WhatsApp message by its id" gives a specific verb (look up) and a specific resource (delivery status of a WhatsApp message), clearly distinct from the send-oriented siblings. It stops short of naming an alternative (e.g., whatsapp_send_text, which produces the id this tool consumes), so it is clear but not maximally differentiating.

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 only implied: the word "sent" signals this is a follow-up call to a send operation and requires an id produced elsewhere. There is no explicit when-to-use, when-not-to-use, or statement about whether it should be polled repeatedly versus called once after a delay.

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.