Skip to main content
Glama

get_auth_status

Check WhatsApp Web login status by opening the browser interface when required. This tool verifies authentication completion for the WhatsApp MCP Server.

Instructions

Open WhatsApp Web if needed and report whether login is complete.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler implementation for get_auth_status which checks the authentication state of the WhatsApp client.
    async def get_auth_status(self) -> dict[str, Any]:
        await self.ensure_started()
        assert self._page is not None
    
        state = await self._detect_state()
    
        return {
            "state": state,
            "base_url": self.settings.base_url,
            "page_url": self._page.url,
            "page_title": await self._page.title(),
  • Registration of the get_auth_status tool within the MCP server definition.
    "get_auth_status": ToolDefinition(
        name="get_auth_status",
        description="Open WhatsApp Web if needed and report whether login is complete.",
        input_schema={"type": "object", "properties": {}, "additionalProperties": False},
        handler=lambda _: self.client.get_auth_status(),
    ),
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It discloses that the tool may open WhatsApp Web and reports login status, but lacks details on behavioral traits such as side effects (e.g., browser automation, potential delays), error handling, or what 'report' entails. For a tool with no annotations, this is insufficient to fully inform an agent.

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, clear sentence that efficiently conveys the tool's purpose without unnecessary words. It is front-loaded with the core action and condition, making it easy to parse. Every part of the sentence earns its place by specifying the tool's behavior.

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

Completeness3/5

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

Given the tool has no parameters, no annotations, and no output schema, the description provides basic context but lacks completeness. It doesn't explain what the output looks like (e.g., boolean status, detailed report) or potential errors. For a tool that interacts with external systems like WhatsApp Web, more detail on behavior and results would be beneficial.

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 tool has 0 parameters, and schema description coverage is 100%, so no parameter documentation is needed. The description doesn't add parameter semantics, but that's acceptable here. A baseline of 4 is appropriate since the schema fully covers the absence of parameters, and the description doesn't need to compensate.

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 tool's purpose: 'Open WhatsApp Web if needed and report whether login is complete.' It specifies the action (open WhatsApp Web conditionally and report login status) and the resource (WhatsApp Web). However, it doesn't explicitly differentiate from sibling tools like 'wait_until_ready' which might also involve readiness checks, so it doesn't reach the highest score.

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 implies usage context: use this tool to check login status, possibly before other operations. It suggests a conditional action ('if needed'), but doesn't provide explicit guidance on when to use it versus alternatives like 'wait_until_ready' or prerequisites for other tools like 'send_message'. The guidance is present but not comprehensive.

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/ekaksher/whatsapp-mcp'

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