Skip to main content
Glama
razvangirgiz

wazap-mcp

by razvangirgiz
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Manage a WhatsApp chat

manage_chat

Toggle a WhatsApp chat's state: archive/unarchive, pin/unpin, mute/unmute, or mark read/unread. Provides chat management for AI agents.

Instructions

Change the state of a chat: archive/unarchive, pin/unpin, mute/unmute (mute_hours defaults to 8), mark_read (sends read receipts) or mark_unread.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
actionYesWhat to do with the chat
chat_idYesChat id as returned by another tool ("<digits>@s.whatsapp.net" or "<id>@g.us"), or a phone number in international format
account_idNoRegistry account id (default, work, …). Omit to resolve from chat_id or message_id, or the default account.
mute_hoursNoHours to mute, default 8; only used by "mute"

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.15.0
    • addedInput schema / properties / account_id
      Added value: +{
+  "description": "Registry account id (default, work, …). Omit to resolve from chat_id or message_id, or the default account.",
+  "minLength": 1,
+  "type": "string"
+}
  2. First observedv0.9.3

TDQS

A3.9/5.0
Behavior4/5

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

Annotations declare the write/non-idempotent/non-destructive profile, and the description adds genuine side-effect detail: mark_read sends read receipts and mute defaults to 8 hours. It stops short of stating reversibility or permission requirements, but it goes beyond the annotations meaningfully.

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?

A single front-loaded sentence that packs the action list and two key defaults without padding. The dense parentheticals cost a little readability but every clause carries information.

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?

For a 4-param mutation tool with full schema coverage and no output schema, the description covers actions, defaults and visible side effects. Auth requirements and whether archived/muted state is reversible are the only real gaps.

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%, so the parameters are already documented. The only added meaning is that mark_read triggers read receipts; the mute_hours default of 8 merely restates the schema, so baseline 3 applies.

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?

States a concrete verb+resource ('Change the state of a chat') and enumerates every supported mutation (archive/pin/mute/mark_read and inverses), so the agent immediately knows the scope. It is clearly separable from siblings like manage_group or send_message.

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?

The list of actions implies when the tool applies, but there is no explicit statement of when to choose this over alternatives (e.g. manage_group for group-level settings) or any prerequisites. Usage must be inferred from the action enum.

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