Skip to main content
Glama
lanchuske

Pilot MCP

by lanchuske
OverviewSchemaRelated ServersScoreDiscussions
JavaScript
Local

whatsapp_search_messages

Search WhatsApp messages to find specific conversations or content by keyword.

Instructions

Search WhatsApp messages

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • server.js:86-86 (registration)
    Tool registration entry in the TOOLS array. The tool is named 'whatsapp_search_messages' with description 'Search WhatsApp messages'.
    ["whatsapp_search_messages", "Search WhatsApp messages"],
  • server.js:106-109 (handler)
    Generic stub handler for all tools. When 'whatsapp_search_messages' is invoked, it returns a static message directing the user to install the real Local MCP binary. The real implementation is in a native binary (macOS/Windows/Linux) not present 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.9/5.0
Behavior2/5

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

With no annotations, the description only implies a read operation ('Search') but does not state behavioral traits like authentication requirements, rate limits, or whether it returns message content or metadata. Minimal disclosure.

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 very concise (two words), but it is too brief for a tool with no schema details. While brevity is valued, it lacks explanatory depth.

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

Completeness1/5

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

For a search tool with no parameters and no output schema, the description is severely incomplete. It does not specify how the search works, what filters can be applied, or what the return format is. Completely inadequate.

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 zero parameters, so no parameter explanation is needed. Baseline 4 applies as per rule.

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 clearly states the action (Search) and resource (WhatsApp messages). It distinguishes itself from general search_messages by specifying WhatsApp, but lacks details on search scope or criteria.

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 is provided on when to use this tool versus alternatives like search_messages or whatsapp_list_chats. There is no mention 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