Skip to main content
Glama
wazap-mcp

wazap-mcp

by razvangirgiz

Learn how to use the WhatsApp tools

learn
Read-onlyIdempotent

Get guidance on WhatsApp IDs, workflows, and error codes, or list available topics when no topic is given; never accesses or changes WhatsApp.

Instructions

The guide, one topic at a time: ids (formats, several accounts, the message shape), workflows, errors (what to do about each code), or all. Call it when unsure about ids, several accounts or an error code; with no topic it lists the topics. Never touches 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": "learn"
  }
}

Input Schema

NameRequiredDescriptionDefault
topicNoNo topic: the list of topics
account_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.7.4
    • removedInput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
    • addedInput schema / properties / topic
      Added value: +{
      +  "description": "No topic: the list of topics",
      +  "enum": [
      +    "ids",
      +    "workflows",
      +    "errors",
      +    "all"
      +  ],
      +  "type": "string"
      +}
  2. Changed1 schema field changedv1.6.0
    • removedInput schema / properties / account_id / description
      Removed value: -"Account id"
  3. Changed1 schema field changedv1.0.3
    • changedInput schema / properties / account_id / description
      Previous value: -"Registry account id (default, work, …). Omit to resolve from chat_id or message_id, or the default account."New value: +"Account id"
  4. Changed2 schema fields changedv0.15.0
    • addedInput schema / additionalProperties
      Added value: +false
    • 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"
      +}
  5. First observedv0.9.3

TDQS

A3.6/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 bar is lower. The description adds genuine context with 'Never touches WhatsApp,' which reassures the agent this call produces no side effects on the account, and it discloses the no-argument discovery behavior. It does not say how large the guide output is or how to read the returned content, which would be the most useful remaining behavioral detail.

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?

Essentially two tight sentences, front-loaded with what the tool is and followed by the call condition and the safety note. The parenthetical topic glosses are dense but each earns its place by disambiguating an enum value. Minor cost: the parenthetical nesting makes the first sentence slightly harder to parse than needed.

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 read-only help tool with no output schema, the description covers the essentials: what topics exist, what each contains, what happens with no topic, and that nothing is mutated. The only material gap is the unexplained `account_id` parameter, whose purpose an agent must guess when it is targeting a specific linked account.

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 50% with only two parameters. The description meaningfully annotates the `topic` values beyond the bare enum (ids covers formats/several accounts/message shape, errors covers 'what to do about each code'), which is real added value. The `account_id` parameter, however, is never mentioned in the description and has no schema description, leaving its role (scoping guidance to a specific linked account) to be inferred.

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?

The description names the resource precisely (a guide) and enumerates its four topics with a short gloss for each, so an agent knows exactly what it retrieves. It also distinguishes itself from every sibling by stating it 'Never touches WhatsApp,' making it the only non-operational tool. The only weakness is that the verb is implicit ('The guide...' rather than 'Get the guide'), but the intent is unambiguous.

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?

It gives concrete trigger conditions: call it 'when unsure about ids, several accounts or an error code,' and documents the zero-argument default ('with no topic it lists the topics'). No explicit when-not guidance or named alternatives are provided, but no sibling plausibly competes for this call, so the guidance is operationally clear.

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