Skip to main content
Glama

waha_get_all_presence

Retrieve all subscribed presence data from WhatsApp contacts to monitor availability status and online activity through the WAHA MCP Server.

Instructions

Get all subscribed presence information.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • MCP tool handler for 'waha_get_all_presence'. Calls WAHAClient.getAllPresence() and returns formatted JSON response.
    private async handleGetAllPresence(args: any) {
      const presences = await this.wahaClient.getAllPresence();
    
      return {
        content: [
          {
            type: "text",
            text: `All subscribed presence information:\n${JSON.stringify(presences, null, 2)}`,
          },
        ],
      };
    }
  • src/index.ts:1156-1157 (registration)
    Tool registration in the CallToolRequestSchema switch statement, dispatching to the handler.
      return await this.handleGetAllPresence(args);
    default:
  • Tool schema definition in ListToolsRequestSchema response, specifying name, description, and empty input schema.
        name: "waha_get_all_presence",
        description: "Get all subscribed presence information.",
        inputSchema: {
          type: "object",
          properties: {},
        },
      },
    ],
  • WAHAClient helper method that makes GET request to /api/{session}/presence to fetch all presence data.
    async getAllPresence(): Promise<any[]> {
      const endpoint = `/api/${this.session}/presence`;
    
      return this.request<any[]>(endpoint, {
        method: "GET",
      });
    }
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states it's a read operation ('Get'), but doesn't mention potential side effects, rate limits, authentication needs, or what 'subscribed presence information' entails. This leaves significant gaps for an AI agent to understand the tool's behavior.

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 that directly states the tool's purpose without any unnecessary words. It's appropriately sized for a no-parameter tool and front-loaded with the core action.

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 and no output schema, the description is minimally adequate but lacks depth. It doesn't explain what 'presence information' includes, how it's formatted, or how it relates to other presence tools, leaving the agent with incomplete context for effective use.

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 the input schema has 100% description coverage (though empty). The description doesn't need to add parameter details, so it meets the baseline expectation. No extra credit is given since there are no parameters to explain.

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 verb 'Get' and the resource 'all subscribed presence information', making the purpose understandable. However, it doesn't explicitly differentiate from sibling tools like 'waha_get_presence' or 'waha_set_presence', which would be needed for a perfect score.

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?

The description provides no guidance on when to use this tool versus alternatives. There's no mention of prerequisites (e.g., needing to subscribe first with 'waha_subscribe_presence'), nor does it explain how this differs from 'waha_get_presence' or other related tools.

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

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