Skip to main content
Glama
wazap-mcp

wazap-mcp

by razvangirgiz

Search WhatsApp messages

search
Read-onlyIdempotent

Find WhatsApp messages by meaning or exact words, with nearby source context and citations, and flag ambiguous matches for verification.

Instructions

Find by meaning and words, with nearby source contexts. Use the question and known context, never guessed filters. Auto: exact codes/quoted literals; words: substrings. Check corrections; assessment flags ambiguity. Cite the supporting message.

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": {
      "query": "<query>"
    },
    "name": "search"
  }
}

Input Schema

NameRequiredDescriptionDefault
tagNoOnly chats with people filed under this tag
fromNo"me", a number, an id, or a name only one person has
limitNo
matchNoauto: questions by meaning, codes/quotes by wordsauto
queryYes
sinceNoISO date or time
untilNoISO date or time
beforeNoOlder lexical matches; auto uses words with a cursor
chat_idNoChat id, number or name (one chat only)
full_textNoEach message's text whole; a list cuts long ones otherwise
account_idNo
include_contextNoNearby sources for the best five hits

Output Schema

NameRequiredDescriptionDefault
modeYeskeyword_fallback: meaning search could not run, see recall_unavailable
syncYes
countYes
indexNo
notesNoCaveats to act on or tell the user
queryYes
contextsNo
coverageNonull: it could not be counted
messagesYes
resolvedNochat_id was a name: the chat it resolved to
freshnessYes
account_idYes
assessmentYes
next_beforeNo
scan_cappedNoOlder matches may be missing: narrow the search
from_resolvedNo
private_omittedNoMatches from people tagged #private, left out: chat_id or from shows them
searched_back_toNoOlder messages were not searched: narrow the search
recall_unavailableNo
changed_during_readNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed21 schema fields changedv1.7.4
    • removedInput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
    • changedInput schema / properties / chat_id / description
      Previous value: -"Chat id, or a phone number"New value: +"Chat id, number or name (one chat only)"
    • removedOutput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
    • addedOutput schema / properties / contexts / items / properties / later
      Added value: +{
      +  "items": {
      +    "additionalProperties": {},
      +    "properties": {
      +      "chat_id": {
      +        "type": "string"
      +      },
      +      "message_id": {
      +        "type": "string"
      +      },
      +      "text": {
      +        "type": "string"
      +      },
      +      "timestamp": {
      +        "type": "string"
      +      }
      +    },
      +    "required": [
      +      "message_id",
      +      "chat_id",
      +      "text",
      +      "timestamp"
      +    ],
      +    "type": "object"
      +  },
      +  "type": "array"
      +}
    • changedOutput schema / properties / contexts / items / properties / messages / items / additionalProperties
      Previous value: -trueNew value: +{}
    • changedOutput schema / properties / coverage / anyOf
      Previous value: -[
      -  {
      -    "additionalProperties": true,
      -    "properties": {},
      -    "type": "object"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]New value: +[
      +  {
      +    "additionalProperties": {},
      +    "properties": {},
      +    "type": "object"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • changedOutput schema / properties / freshness / anyOf
      Previous value: -[
      -  {
      -    "$ref": "#/properties/coverage/anyOf/0"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]New value: +[
      +  {
      +    "additionalProperties": {},
      +    "properties": {},
      +    "type": "object"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • removedOutput schema / properties / index / $ref
      Removed value: -"#/properties/coverage/anyOf/0"
    • addedOutput schema / properties / index / additionalProperties
      Added value: +{}
    • addedOutput schema / properties / index / properties
      Added value: +{}
    • addedOutput schema / properties / index / type
      Added value: +"object"
    • changedOutput schema / properties / messages / items / additionalProperties
      Previous value: -trueNew value: +{}
    • removedOutput schema / properties / messages / items / properties / chat_id / $ref
      Removed value: -"#/properties/contexts/items/properties/messages/items/properties/chat_id"
    • addedOutput schema / properties / messages / items / properties / chat_id / type
      Added value: +"string"
    • removedOutput schema / properties / messages / items / properties / message_id / $ref
      Removed value: -"#/properties/contexts/items/properties/messages/items/properties/message_id"
    • addedOutput schema / properties / messages / items / properties / message_id / type
      Added value: +"string"
    • removedOutput schema / properties / messages / items / properties / text / $ref
      Removed value: -"#/properties/contexts/items/properties/messages/items/properties/text"
    • addedOutput schema / properties / messages / items / properties / text / type
      Added value: +"string"
    • removedOutput schema / properties / messages / items / properties / timestamp / $ref
      Removed value: -"#/properties/contexts/items/properties/messages/items/properties/timestamp"
    • addedOutput schema / properties / messages / items / properties / timestamp / type
      Added value: +"string"
    • addedOutput schema / properties / resolved
      Added value: +{
      +  "additionalProperties": false,
      +  "description": "chat_id was a name: the chat it resolved to",
      +  "properties": {
      +    "from": {
      +      "type": "string"
      +    },
      +    "kind": {
      +      "enum": [
      +        "person",
      +        "group"
      +      ],
      +      "type": "string"
      +    },
      +    "name": {
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "from",
      +    "name",
      +    "kind"
      +  ],
      +  "type": "object"
      +}
  2. Changed21 schema fields changedv1.6.0
    • removedInput schema / properties / account_id / description
      Removed value: -"Account id"
    • addedInput schema / properties / before
      Added value: +{
      +  "description": "Older lexical matches; auto uses words with a cursor",
      +  "minLength": 5,
      +  "type": "string"
      +}
    • addedInput schema / properties / include_context
      Added value: +{
      +  "default": true,
      +  "description": "Nearby sources for the best five hits",
      +  "type": "boolean"
      +}
    • changedInput schema / properties / match / default
      Previous value: -"hybrid"New value: +"auto"
    • changedInput schema / properties / match / description
      Previous value: -"\"words\": only messages holding the words"New value: +"auto: questions by meaning, codes/quotes by words"
    • changedInput schema / properties / match / enum
      Previous value: -[
      -  "hybrid",
      -  "words"
      -]New value: +[
      +  "auto",
      +  "hybrid",
      +  "words"
      +]
    • addedInput schema / properties / tag
      Added value: +{
      +  "description": "Only chats with people filed under this tag",
      +  "maxLength": 40,
      +  "minLength": 1,
      +  "type": "string"
      +}
    • addedOutput schema / properties / assessment
      Added value: +{
      +  "additionalProperties": false,
      +  "properties": {
      +    "note": {
      +      "type": "string"
      +    },
      +    "state": {
      +      "enum": [
      +        "no_matches",
      +        "ambiguous",
      +        "candidates"
      +      ],
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "state",
      +    "note"
      +  ],
      +  "type": "object"
      +}
    • addedOutput schema / properties / changed_during_read
      Added value: +{
      +  "type": "boolean"
      +}
    • addedOutput schema / properties / contexts
      Added value: +{
      +  "items": {
      +    "additionalProperties": false,
      +    "properties": {
      +      "anchor_id": {
      +        "type": "string"
      +      },
      +      "bounded": {
      +        "const": true,
      +        "type": "boolean"
      +      },
      +      "messages": {
      +        "items": {
      +          "additionalProperties": true,
      +          "properties": {
      +            "chat_id": {
      +              "type": "string"
      +            },
      +            "message_id": {
      +              "type": "string"
      +            },
      +            "text": {
      +              "type": "string"
      +            },
      +            "timestamp": {
      +              "type": "string"
      +            }
      +          },
      +          "required": [
      +            "message_id",
      +            "chat_id",
      +            "text",
      +            "timestamp"
      +          ],
      +          "type": "object"
      +        },
      +        "type": "array"
      +      }
      +    },
      +    "required": [
      +      "anchor_id",
      +      "messages",
      +      "bounded"
      +    ],
      +    "type": "object"
      +  },
      +  "type": "array"
      +}
    • addedOutput schema / properties / messages / items / properties / chat_id / $ref
      Added value: +"#/properties/contexts/items/properties/messages/items/properties/chat_id"
    • removedOutput schema / properties / messages / items / properties / chat_id / type
      Removed value: -"string"
    • addedOutput schema / properties / messages / items / properties / message_id / $ref
      Added value: +"#/properties/contexts/items/properties/messages/items/properties/message_id"
    • removedOutput schema / properties / messages / items / properties / message_id / type
      Removed value: -"string"
    • addedOutput schema / properties / messages / items / properties / rank_score
      Added value: +{
      +  "type": "number"
      +}
    • addedOutput schema / properties / messages / items / properties / text / $ref
      Added value: +"#/properties/contexts/items/properties/messages/items/properties/text"
    • removedOutput schema / properties / messages / items / properties / text / type
      Removed value: -"string"
    • addedOutput schema / properties / messages / items / properties / timestamp / $ref
      Added value: +"#/properties/contexts/items/properties/messages/items/properties/timestamp"
    • removedOutput schema / properties / messages / items / properties / timestamp / type
      Removed value: -"string"
    • addedOutput schema / properties / next_before
      Added value: +{
      +  "type": [
      +    "string",
      +    "null"
      +  ]
      +}
    • changedOutput schema / required
      Previous value: -[
      -  "query",
      -  "mode",
      -  "count",
      -  "messages",
      -  "freshness",
      -  "sync",
      -  "account_id"
      -]New value: +[
      +  "query",
      +  "mode",
      +  "count",
      +  "assessment",
      +  "messages",
      +  "freshness",
      +  "sync",
      +  "account_id"
      +]
  3. Changed1 schema field changedv1.4.0
    • addedInput schema / properties / full_text
      Added value: +{
      +  "description": "Each message's text whole; a list cuts long ones otherwise",
      +  "type": "boolean"
      +}
  4. Addedv1.0.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 open-world, so the safety profile is covered. The description adds real behavioral detail beyond that: how auto mode resolves codes/quoted literals to word matching, that words match as substrings, that ambiguity is flagged, and that the response should be cited back to a supporting message. It stops short of describing result ordering, cursor behavior beyond the vague "before" hint, or failure modes.

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?

Front-loaded with the core purpose and kept to a handful of short clauses with almost no filler. Some fragments ("Check corrections; assessment flags ambiguity") are compressed to the point of being cryptic, costing a little clarity for the density gained.

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?

An output schema and rich annotations mean the description need not explain return values, and it correctly focuses on query construction and mode semantics. For a 12-parameter tool it is still thin on scoping and pagination behavior (limit, since/until, tag, from), leaving an agent to lean entirely on the schema for the majority of filters.

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?

With 75% schema coverage the schema already explains tag, from, match, include_context, full_text, chat_id and before. The description adds only marginal meaning, notably that words matching means substrings and that contexts accompany the "best five hits"; it says nothing about limit, since/until, or account_id. Baseline 3 is appropriate when the schema carries most of the load.

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 ("Find") and two search modes ("by meaning and words") plus that it returns nearby source contexts, which tells an agent this is a retrieval tool distinct from read_messages/get_message. It never names the resource (messages) itself, relying on the title and sibling set for that, so it falls short of a fully self-contained 5.

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?

"Use the question and known context, never guessed filters" is actionable guidance on how to construct the query and a clear prohibition against inventing filters. It does not say when to prefer this over siblings such as read_messages or catch_up, so the alternative-selection guidance is implied rather than stated.

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