Skip to main content
Glama
wazap-mcp

wazap-mcp

by razvangirgiz

Remember something about a person

remember
Idempotent

Save local notes, tags, and contact details for WhatsApp chats without sending them to WhatsApp; mark asks handled and exclude flagged contacts from catch-up.

Instructions

Keep what the user says about someone, locally, never on WhatsApp: a note, tags, details find_contact matches ({"relatie": "mama"}), or handled: true for an ask dealt with elsewhere. #private keeps their words out of what you did not ask about them by name; #no-catchup keeps them out of catch_up.

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": {
      "chat_id": "<chat_id>"
    },
    "name": "remember"
  }
}

Input Schema

NameRequiredDescriptionDefault
noteNo"" removes it
fieldsNoe.g. {"nickname": "Mișu", "role": "contabil"}; "" deletes a key
chat_idYesSeveral: tags and fields only
handledNoOff catch_up's waiting until they write again
add_tagsNoe.g. ["client"]
account_idNo
remove_tagsNo
remove_fieldsNo

Output Schema

NameRequiredDescriptionDefault
nameNo
noteNo
tagsNo
fieldsNo
numberNo
peopleNoSeveral chat_ids: each one's card
chat_idNo
handledNoThe ask taken off the waiting list; null when nothing was open
account_idYes
is_businessNo
is_my_contactNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changedv1.7.4
    • removedInput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
    • changedInput schema / properties / chat_id / anyOf
      Previous value: -[
      -  {
      -    "description": "Chat id, or a phone number",
      -    "minLength": 1,
      -    "type": "string"
      -  },
      -  {
      -    "items": {
      -      "$ref": "#/properties/chat_id/anyOf/0"
      -    },
      -    "maxItems": 50,
      -    "minItems": 1,
      -    "type": "array"
      -  }
      -]New value: +[
      +  {
      +    "description": "Chat id, or a phone number",
      +    "minLength": 1,
      +    "type": "string"
      +  },
      +  {
      +    "items": {
      +      "description": "Chat id, or a phone number",
      +      "minLength": 1,
      +      "type": "string"
      +    },
      +    "maxItems": 50,
      +    "minItems": 1,
      +    "type": "array"
      +  }
      +]
    • addedInput schema / properties / fields / propertyNames
      Added value: +{
      +  "type": "string"
      +}
    • removedOutput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
    • addedOutput schema / properties / fields / propertyNames
      Added value: +{
      +  "type": "string"
      +}
    • changedOutput schema / properties / people / items / additionalProperties
      Previous value: -trueNew value: +{}
  2. Changed7 schema fields changedv1.6.0
    • removedInput schema / properties / account_id / description
      Removed value: -"Account id"
    • addedInput schema / properties / chat_id / anyOf
      Added value: +[
      +  {
      +    "description": "Chat id, or a phone number",
      +    "minLength": 1,
      +    "type": "string"
      +  },
      +  {
      +    "items": {
      +      "$ref": "#/properties/chat_id/anyOf/0"
      +    },
      +    "maxItems": 50,
      +    "minItems": 1,
      +    "type": "array"
      +  }
      +]
    • changedInput schema / properties / chat_id / description
      Previous value: -"Chat id, or a phone number"New value: +"Several: tags and fields only"
    • removedInput schema / properties / chat_id / minLength
      Removed value: -1
    • removedInput schema / properties / chat_id / type
      Removed value: -"string"
    • addedOutput schema / properties / people
      Added value: +{
      +  "description": "Several chat_ids: each one's card",
      +  "items": {
      +    "additionalProperties": true,
      +    "properties": {},
      +    "type": "object"
      +  },
      +  "type": "array"
      +}
    • changedOutput schema / required
      Previous value: -[
      -  "chat_id",
      -  "name",
      -  "account_id"
      -]New value: +[
      +  "account_id"
      +]
  3. Addedv1.0.3

TDQS

A3.7/5.0
Behavior4/5

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

Annotations only declare the mutation/idempotency profile; the description adds real behavior beyond that — data is stored locally and never sent to WhatsApp, '#private' restricts the stored words from unrelated queries, '#no-catchup' removes the person from catch_up, and '""' deletes a note or field key. These are meaningful privacy and side-effect disclosures. It still doesn't say what a successful write returns or how conflicting concurrent writes behave.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Every clause carries information, but the second sentence is convoluted ('keeps their words out of what you did not ask about them by name') and introduces hashtag directives and inline JSON without setup. The core purpose is front-loaded, yet the flag semantics would read better as a short list than as one packed sentence.

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 an 8-parameter mutation tool, the description covers purpose, storage scope, the two privacy flags, deletion semantics, and the find_contact/catch_up relationships, while annotations carry safety and an output schema carries return values. Remaining gaps — remove_tags/remove_fields, account_id, and array chat_id constraints — are documented in the schema rather than the prose.

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?

With 63% schema coverage, the description pulls extra weight: it explains that fields are the details find_contact matches (with a concrete {"relatie": "mama"} example), that handled:true suppresses catch_up's waiting, and that an empty string removes a note or deletes a key. remove_tags, remove_fields, account_id and the multi-chat_id behavior are left to the schema, so it does not fully close the gap.

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 (what the user says about someone) and the concrete payloads stored — a note, tags, fields that find_contact matches, or handled:true. It also distinguishes the tool from siblings by name (find_contact, catch_up) and states the storage boundary ('locally, never on WhatsApp'). The verb 'keep' is vaguer than 'store/update' and the sentence is dense, which keeps it below a 5.

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?

Usage is implied through the flags: '#no-catchup keeps them out of catch_up' and 'handled: true for an ask dealt with elsewhere' route the agent relative to catch_up, and the find_contact reference hints at lookup-then-store flow. However, there is no explicit statement of when to call remember versus find_contact or learn, and no exclusions or prerequisites are spelled out.

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