Fetch all WhatsApp chats involving a specific contact by JID, with pagination and limit controls, enabling quick retrieval of conversation history.
Get all WhatsApp chats involving the contact.
Args:
jid: The contact's JID to search for
limit: Maximum number of chats to return (default 20)
page: Page number for pagination (default 0)
| Name | Required | Description | Default |
|---|---|---|---|
| jid | Yes | ||
| page | No | ||
| limit | No |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full burden. It indicates a read-style operation and documents pagination defaults, but it does not disclose return shape, ordering, permissions, or whether it includes group and direct chats.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is short and front-loaded with the core action, followed by a compact Args section. Every sentence and parameter entry adds useful information with no filler.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a three-parameter read tool with no annotations and no output schema, the description covers purpose and parameters but leaves return structure and behavioral edge cases unspecified. It is minimally adequate but not fully complete.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 0%, so the description must compensate. It explains all three parameters: jid as the contact JID to search for, limit as the maximum chats to return with default 20, and page for pagination with default 0.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description states a specific verb and resource: 'Get all WhatsApp chats involving the contact.' This is clear enough for an agent to understand the operation, but it does not distinguish this tool from siblings such as get_direct_chat_by_contact or list_chats.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description gives no explicit guidance on when to use this tool versus alternatives like get_direct_chat_by_contact or list_chats. It implies retrieving chats for a contact but provides no exclusions or routing conditions.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.