WhatsApp MCP Stream

list_chats

Read-onlyIdempotent

List WhatsApp chats with optional limit and last message details.

Instructions

Get WhatsApp chats, optionally filtered and sorted.

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

Input Schema

Name	Required	Description	Default
`limit`	No	Maximum number of chats to return
`include_last_message`	No	Whether to include the last message details

Schema Changelog

Changes observed during successful MCP inspections.

AddedApr 30, 2026

TDQS

C2.9/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true and idempotentHint=true, so the agent knows it's a safe read. The description adds 'optionally filtered and sorted' which is not reflected in schema, but does not contradict annotations. No additional behavioral context (e.g., pagination, response format) is provided.

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?

The description is a single short sentence, which is concise, but the ambiguous 'filtered and sorted' could be removed or clarified. It is front-loaded with the main action.

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?

Given the simple tool with 2 well-documented parameters and clear annotations, the description covers the basic purpose but omits response structure (no output schema) and does not clarify the mismatch between description and schema regarding filtering/sorting. Adequate but not complete.

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 100% and both parameters have descriptions. The description's mention of 'filtered and sorted' does not correspond to actual parameters, and adds no semantic value beyond what the schema already provides.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states 'Get WhatsApp chats' which is clear on verb and resource. However, it adds 'optionally filtered and sorted' but the schema only includes limit and include_last_message, with no filter or sort parameters. This mismatch can confuse an agent expecting filtering capabilities.

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?

No guidance on when to use this tool versus siblings like get_chat_by_contact, list_groups, or list_system_chats. The description does not mention use cases, exclusions, or alternatives.

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