Skip to main content
Glama
lanchuske

Pilot MCP

by lanchuske
OverviewSchemaRelated ServersScoreDiscussions
JavaScript
Local

whatsapp_list_chats

Retrieve a list of your WhatsApp conversations to manage or search through messages.

Instructions

List WhatsApp conversations

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • server.js:84-84 (registration)
    The tool 'whatsapp_list_chats' is registered in the TOOLS array with description 'List WhatsApp conversations'. It is part of a stub/inspection server that returns a placeholder message rather than real logic.
    ["whatsapp_list_chats", "List WhatsApp conversations"],
  • server.js:106-109 (handler)
    The handler for all tools (including whatsapp_list_chats) is a stub that returns a message to install the real Local MCP package. There is no actual WhatsApp integration in this codebase.
    for (const [name, desc] of TOOLS) {
  server.tool(name, desc, {}, async () => ({
    content: [{ type: "text", text: "This is an inspection stub. Install Local MCP: npx -y local-mcp@latest setup" }],
  }));

Tool Definition Quality

C2.8/5.0
Behavior1/5

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

With no annotations, the description must disclose behavioral traits. It fails to mention if all conversations are returned, if there is filtering, pagination, or what side effects (if any) occur. The tool's behavior is opaque.

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, efficient sentence. It is front-loaded with the key action and resource. However, given the tool's simplicity, the extreme brevity leaves out important details that could be included without losing conciseness.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Even for a simple list tool, the description lacks information about the output format, whether it returns all chats or just recent ones, and any ordering. With no output schema or annotations, the description should compensate but does not.

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

Parameters4/5

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

The input schema has no parameters, so schema description coverage is 100% by default. The description adds no new parameter information, but the baseline score of 4 applies because no parameters exist to describe.

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 'List WhatsApp conversations' clearly states the action (list) and resource (WhatsApp conversations). It distinguishes from sibling tools like whatsapp_read_messages and whatsapp_send_message by focusing on listing rather than reading or sending. However, it does not explicitly detail what is included in conversations (e.g., archived, deleted).

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 usage guidance is provided. The description does not mention when to use this tool versus alternatives like list_message_chats or other platform-specific list tools. There is no indication of prerequisites or context.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/lanchuske/local-mcp-releases'

If you have feedback or need assistance with the MCP directory API, please join our Discord server