WhatsApp MCP Stream

logout

DestructiveIdempotent

End your current WhatsApp session and clear session data. Optionally provide an idempotency key to avoid duplicate logouts.

Instructions

Logout from WhatsApp and clear the current session

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

Input Schema

Name	Required	Description	Default
`idempotency_key`	No	Optional idempotency key. Repeating the same logout request with the same key returns the original result instead of logging out again.

Schema Changelog

Changes observed during successful MCP inspections.

AddedApr 30, 2026

TDQS

A3.6/5.0

Behavior3/5

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

Annotations already indicate destructiveHint=true and idempotentHint=true. The description adds 'clear the current session' which aligns with destruction but does not disclose additional behavioral traits such as authentication requirements or rate limits. It is consistent but adds limited value beyond annotations.

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, front-loaded sentence with no wasted words. It efficiently communicates the purpose and effect.

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

Completeness4/5

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

For a simple logout tool with annotations covering safety and idempotency, the description is adequate. It explains the core effect. However, it does not describe potential side effects (e.g., clearing caches, disconnecting) or output behavior, which would be needed for a perfect score.

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?

There is only one parameter (idempotency_key) with 100% schema coverage via its own description. The tool description does not mention or elaborate on the parameter, but the schema already provides sufficient meaning. Thus the description adds no extra parameter semantics, meeting the baseline for high coverage.

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

Purpose5/5

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

The description clearly states the action ('Logout from WhatsApp') and the effect ('clear the current session'), using a specific verb and resource. It is distinct from all sibling tools, which focus on chats, contacts, and messaging, not session management.

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 explicit guidance is provided on when to use this tool versus alternatives, nor any exclusions or prerequisites. The description assumes the agent knows when logout is appropriate, which is reasonable for this simple action but still lacks explicit direction.

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