Skip to main content
Glama
whatsapp-localmind

whatsapp-localmind

by qilaidev

whatsapp_search_messages

Search keywords across allowed WhatsApp group chats to find matching messages with surrounding context, filterable by time window and chat.

Instructions

Search keyword across allowed WhatsApp group chats and return matching messages with surrounding context messages.

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

Input Schema

NameRequiredDescriptionDefault
limitNo
queryYesKeyword to search in message text and attachment titles.
sinceNoOptional time window filter (e.g. '30d', '7d').
formatNomarkdown
contextNoNumber of before/after context messages per match (default 3).
chat_idsNoOptional list of group chat_ids (@g.us) or ['ALL_ALLOWED'].

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv3.2.0

TDQS

B3.4/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden; it does disclose that results are scoped to 'allowed' chats and include surrounding context. It does not cover ordering, pagination behavior, rate limits, or what happens when the keyword matches nothing, leaving meaningful behavioral gaps for an unannotated tool.

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

Conciseness5/5

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

A single front-loaded sentence with no filler; the scope and the returned payload are stated up front and nothing redundant is included.

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 6-parameter search tool with no output schema and no annotations, the description states what is returned ('matching messages with surrounding context messages') and the search scope, which is the core an agent needs. It is incomplete on pagination, result ordering and the limit/format parameters, but the essentials are present.

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 67% schema coverage the schema does most of the work, documenting query, since, context, format and chat_ids. The description adds only the 'allowed group chats' framing for chat_ids and says nothing about limit defaults, time-window syntax, or the markdown/json format choice.

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 a specific verb and resource ('Search keyword ... messages') and scopes it to 'allowed WhatsApp group chats', which separates it from a plain fetch tool. It does not explicitly name a sibling to contrast with, so it stops short of 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 Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use or when-not-to-use guidance and no mention of alternatives such as fetch_messages for unfiltered retrieval. 'Allowed' hints at a permission boundary but does not tell the agent when to pick this tool over browsing a chat.

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