Skip to main content
Glama
Sign In
Convertway WhatsApp MCP Server

Convertway WhatsApp MCP Server

by QalaLabs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

get_delivery_status

Check whether a sent WhatsApp, SMS, or email message was delivered by providing its message ID.

Instructions

Check the delivery status of a previously sent message

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": "get_delivery_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
channelNoChannel the message was sent on
messageIdYesMessage ID returned from a send operation

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.3/5.0
Behavior2/5

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

The description lacks details beyond 'Check'. With no annotations, the description should disclose if the tool is read-only, what status values are returned, or any rate limits. The description simply states the purpose without behavioral context.

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 description is a single, clear sentence with no unnecessary words. It is appropriately sized for the tool's simplicity.

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 simple read tool with two parameters and no output schema, the description is functional but minimal. It does not hint at return values (possible statuses) or usage constraints, leaving the agent without full context.

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 coverage is 100%, so the schema fully describes the parameters. The description adds no extra meaning beyond what the schema provides. Baseline 3 is appropriate.

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 clearly states the tool's purpose: 'Check the delivery status of a previously sent message'. It uses a specific verb ('Check') and resource ('delivery status') and is distinct from sibling tools like 'send_whatsapp' or 'get_conversation_history'.

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

Usage Guidelines2/5

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

No guidance is provided on when to use this tool versus alternatives (e.g., get_conversation_history) or prerequisites (e.g., message must be sent via this system). There is no mention of when not to use it.

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