Perisclaw: Use ChatGPT and Claude with your WhatsApp

List Recent Chats

chats_recent

Read-only

List the operator's WhatsApp chats, MOST RECENT ACTIVITY FIRST — each with chat_id, name, unread_count, last-activity time, and labels. Optionally restrict to chats with unread messages, and cap the count.

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

Input Schema

Name	Required	Description	Default
`limit`	No	Max chats to return. Default 50, max 200.
`unread_only`	No	Only chats with unread messages. Default false.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 2, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds useful behavioral context: results are ordered by most recent activity and include specific fields such as chat_id, name, unread_count, last-activity time, and labels.

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?

The description is a single efficient sentence with the core purpose and ordering front-loaded. Every clause contributes useful information without waste.

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

Completeness5/5

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

For a simple read-only list tool with full parameter schema coverage and annotations covering safety, the description is complete enough. It also compensates for the absence of an output schema by naming the returned fields.

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 description coverage is 100%, so both parameters are already documented in the input schema. The description restates the optional unread restriction and count cap but adds no syntax or format details beyond the schema.

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 states a specific verb and resource: listing the operator's WhatsApp chats, with ordering and returned fields. It is clear what the tool does, but it does not explicitly distinguish itself from the sibling search_chats tool.

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 description mentions optional unread filtering and a count cap, which implies usage for recent-chat listing. However, it gives no explicit guidance on when to use this tool versus search_chats or other chat-related siblings.

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

All Perisclaw: Use ChatGPT and Claude with your WhatsApp tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.