Skip to main content
Glama
billyfranklim1

mcp-evolution

Logout Instance

logout_instance

Disconnects the pinned WhatsApp instance and clears its session, requiring a QR scan to reconnect.

Instructions

Logout the pinned WhatsApp instance (disconnects and clears session — requires QR scan to reconnect).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Registration function for the logout_instance tool. Makes a DELETE request to /instance/logout/{instanceName} to disconnect and clear the WhatsApp session.
    export function registerLogoutInstance(server: McpServer, client: EvolutionClient): void {
      server.registerTool(
        "logout_instance",
        {
          title: "Logout Instance",
          description: "Logout the pinned WhatsApp instance (disconnects and clears session — requires QR scan to reconnect).",
          inputSchema: {},
        },
        async () => {
          try {
            const data = await client.delete(`/instance/logout/${client.instanceName}`);
            return { content: [{ type: "text" as const, text: JSON.stringify(data, null, 2) }] };
          } catch (e) {
            if (e instanceof McpError) return { isError: true, content: [{ type: "text" as const, text: e.message }] };
            throw e;
          }
        }
      );
    }
  • The input schema for logout_instance is an empty object (no parameters needed).
    inputSchema: {},
  • Registration call for logout_instance within the tool registration chain.
    registerLogoutInstance(server, client);
  • Import of the registerLogoutInstance function from the logout-instance module.
    import { registerLogoutInstance } from "./logout-instance.js";
Behavior4/5

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

Without annotations, the description carries the full burden. It discloses that the session is disconnected and cleared requiring a QR scan to reconnect. However, it does not mention potential side effects like message loss or cooldown periods.

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 sentence that is clear and front-loaded with the action. Every word adds value; no fluff.

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 tool with no parameters and no output schema, the description sufficiently explains the action and consequence. It is complete for the tool's complexity.

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?

There are zero parameters, and schema coverage is 100%. The description adds no parameter info, but with no parameters, baseline is 4. The description does not need to elaborate further.

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 verb 'Logout' and the resource 'pinned WhatsApp instance'. It distinguishes itself from siblings like 'restart_instance' by specifying that it disconnects and clears the session, requiring a QR scan to reconnect.

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?

No explicit guidance on when to use this tool versus alternatives (e.g., restart_instance). The description implies usage when a full disconnect and re-authentication is desired, but lacks direct comparisons or exclusions.

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/billyfranklim1/mcp-evolution'

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