Skip to main content
Glama
wazap-mcp

wazap-mcp

by razvangirgiz

List or cancel scheduled WhatsApp messages

scheduled_messages
Idempotent

List upcoming WhatsApp scheduled messages and this week's sent, missed, failed, or cancelled ones, or cancel a pending message by schedule ID before it sends.

Instructions

The account's scheduled messages: list (waiting ones soonest first, then the week's sent, missed, failed and cancelled ones) or cancel one by schedule_id before it goes. To schedule one, send_message with send_at, then confirm_send. Tell the user about every missed or failed one.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "scheduled_messages"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
actionNolist
account_idNo
schedule_idNocancel: from the list or confirm_send
include_closedNolist: the week's closed ones too

Output Schema

NameRequiredDescriptionDefault
countYes
actionYes
cancelledNo
scheduledYes
account_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv1.7.4
    • removedInput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
    • changedInput schema / properties / include_closed / description
      Previous value: -"list: the week's sent, missed, failed and cancelled ones too"New value: +"list: the week's closed ones too"
    • removedOutput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
    • changedOutput schema / properties / scheduled / items / additionalProperties
      Previous value: -trueNew value: +{}
    • changedOutput schema / properties / scheduled / items / properties / to / additionalProperties
      Previous value: -trueNew value: +{}
  2. Changed1 schema field changedv1.6.0
    • removedInput schema / properties / account_id / description
      Removed value: -"Account id"
  3. Addedv1.4.0

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare a mutating-but-non-destructive, idempotent, closed-world tool; the description adds the real behavioral detail: the exact result ordering, which status buckets are returned, and the precondition that cancellation must happen 'before it goes.' It does not spell out what happens if the schedule already fired or whether cancel is reversible, so it stops short of a 5.

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?

Two dense sentences, front-loaded with the operations and their ordering, followed by the alternative path and the user-facing duty. No filler or repetition of the title.

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?

With an output schema present, return values need no explanation, and the description covers ordering, the cancel precondition, and the scheduling alternative. The remaining gap is the unmentioned limit and account_id parameters, which is minor for an otherwise complete definition.

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 only 40% across five parameters, so the description needs to compensate and does so partially: it explains action semantics (list vs cancel), the source of schedule_id ('from the list or confirm_send'), and what include_closed controls ('the week's sent, missed, failed and cancelled ones'). It says nothing about limit or account_id, so the compensation is incomplete.

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 resource (the account's scheduled messages) and both supported operations, then details the listing order (waiting soonest first, then the week's sent, missed, failed and cancelled). This distinguishes it clearly from send_message/confirm_send, which are named as the scheduling path.

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

Usage Guidelines5/5

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

It states explicitly when to use this tool (list or cancel a pending schedule) and routes the alternative case by name: 'To schedule one, send_message with send_at, then confirm_send.' It also gives a usage directive to surface missed/failed items to the user, leaving nothing to inference about the intended workflow.

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