Skip to main content
Glama
wazap-mcp

wazap-mcp

by razvangirgiz

Set, list or cancel a reminder about a chat

reminder

Create chat reminders with a due time or hour offset, and list or cancel them. "no_reply" reminders fire only if nobody wrote in the chat since it was set.

Instructions

The user's reminders about a chat, kept locally and posted to their webhook when due: create (chat_id, note, after_hours or due_at); condition "no_reply" fires only if nobody wrote there since ("if Ana has not answered in 2 days"). list, cancel. Nothing goes to WhatsApp.

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

Input Schema

NameRequiredDescriptionDefault
noteNocreate: the reminder
limitNo
actionNolist
due_atNocreate: "2026-10-14T09:00" in time_zone, or with an offset
chat_idNocreate: the chat it is about
conditionNono_reply: skipped if someone wrote in the chat after it was setalways
time_zoneNoIANA zone for due_at; the server's by default
account_idNo
after_hoursNocreate: due in this many hours
reminder_idNocancel: from create or list
include_closedNolist: the week's closed ones too

Output Schema

NameRequiredDescriptionDefault
countYes
notesNoCaveats to act on or tell the user
actionYes
cancelledNo
remindersYes
account_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changedv1.7.4
    • removedInput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
    • changedInput schema / properties / after_hours / description
      Previous value: -"create: due this many hours from now"New value: +"create: due in this many hours"
    • changedInput schema / properties / due_at / description
      Previous value: -"create: due then, \"2026-10-14T09:00\" in time_zone, or with an offset"New value: +"create: \"2026-10-14T09:00\" in time_zone, or with an offset"
    • changedInput schema / properties / include_closed / description
      Previous value: -"list: the week's fired, skipped and cancelled ones too"New value: +"list: the week's closed ones too"
    • changedInput schema / properties / note / description
      Previous value: -"create: what to remind the user of"New value: +"create: the reminder"
    • removedOutput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
    • changedOutput schema / properties / reminders / items / 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

A3.7/5.0
Behavior3/5

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

Adds real behavior beyond the annotations: reminders live locally, fire via webhook, and no_reply is suppressed if someone wrote in the chat after it was set. Still silent on failure modes, what happens if the webhook is unreachable, or whether a fired reminder is removed. Annotations cover the mutation safety profile (non-destructive, non-idempotent), so the bar is moderate.

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?

Dense but front-loaded, with action names used as anchors. The semicolon-and-parenthesis packing and the trailing "Nothing goes to WhatsApp" line are terse to the point of being cryptic, though nothing is redundant.

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?

With 11 parameters, zero required, and action defaulting to list, the description never states the default or the listing filters (limit, include_closed). The output schema covers return values, so that is not a gap, but the list-mode behavior is underdescribed relative to the tool's complexity.

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

Parameters4/5

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

Clarifies the either/or between after_hours and due_at, groups parameters by action, and explains no_reply with an example sentence. Omits account_id, time_zone, limit and include_closed, whose schema descriptions are thin or absent, leaving those four to inference.

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 set and resource: reminders about a chat, stored locally and delivered to a webhook. "Nothing goes to WhatsApp" implicitly separates it from send_message and scheduled_messages, though the sibling contrast is never named explicitly.

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?

Enumerates the three actions with the parameters each needs (create takes chat_id, note, after_hours or due_at; list; cancel) and gives a concrete scenario for no_reply. No explicit exclusion or routing rule against scheduled_messages, so the agent must infer the boundary.

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