Skip to main content
Glama
Sign In
WhatsApp MCP Server

WhatsApp MCP Server

by HardikCoder45
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

fetch_all_chats

List all chats from your local WhatsApp session cache, bypassing the default limit to access your complete chat list.

Instructions

List ALL chats visible in the local session cache (not capped by the default list).

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

Input Schema

NameRequiredDescriptionDefault
limitNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

B3.3/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose two useful traits: results come from a 'local session cache' and the result set is uncapped. However, it omits the practical consequences of an unbounded fetch (volume, performance, pagination) and whether the cache can be stale relative to server state.

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 sentence with the differentiator front-loaded and zero filler. Nothing to trim and nothing buried.

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?

For a simple zero-required-parameter read tool with no output schema, the description covers the core purpose, but it leaves the one optional parameter unexplained and does not address the sibling list_chats it is clearly meant to complement. Adequate but with visible gaps.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must explain the single 'limit' parameter, and it does not mention it at all. Worse, the headline framing 'List ALL ... not capped' sits in tension with a limit parameter capped at 10000, so the agent gets no guidance on how limit interacts with the 'ALL' framing.

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 clear verb ('List') and resource ('chats') plus the scope qualifier 'ALL ... not capped by the default list'. It implicitly distinguishes itself from the sibling list_chats via the 'default list' reference, though it never names that sibling outright.

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?

The parenthetical '(not capped by the default list)' implies when this tool is preferred — when the default capped listing is insufficient — but it never says to use list_chats otherwise, nor does it name any alternative. Usage is inferable rather than stated.

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

Deploy Server

Other Tools