Skip to main content
Glama
luiso2

Evolution API WhatsApp MCP Server

by luiso2

instance_status

Check the connection status of a WhatsApp Business instance to monitor its availability and ensure reliable messaging operations.

Instructions

Get connection status of an instance

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
instanceNameYesInstance name

Implementation Reference

  • MCP tool handler for 'instance_status' that fetches the instance connection status from EvolutionAPI and returns it as JSON text content.
    private async handleInstanceStatus(args: any) {
      const status = await evolutionAPI.getConnectionStatus(args.instanceName);
      return {
        content: [
          {
            type: 'text',
            text: JSON.stringify(status, null, 2)
          }
        ]
      };
    }
  • src/index.ts:492-493 (registration)
    Switch case that registers and dispatches calls to the 'instance_status' tool handler.
    case 'instance_status':
      return await this.handleInstanceStatus(args);
  • Registration in tools list with input schema requiring 'instanceName' string.
      name: 'instance_status',
      description: 'Get connection status of an instance',
      inputSchema: {
        type: 'object',
        properties: {
          instanceName: { type: 'string', description: 'Instance name' }
        },
        required: ['instanceName']
      }
    },
  • Core helper function that makes HTTP GET request to Evolution API endpoint /instance/connectionState/{instanceName} to retrieve status.
    async getConnectionStatus(instanceName: string): Promise<{
      instance: string;
      state: string;
    }> {
      const response = await this.client.get(`/instance/connectionState/${instanceName}`);
      return response.data;
    }
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 mentions 'Get' which implies a read operation, but doesn't specify if this requires authentication, what the output format might be, or any rate limits. This is a significant gap for a tool with zero annotation coverage.

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 with no wasted words. It's front-loaded with the core purpose, making it highly efficient and easy to parse for an AI agent.

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

Completeness2/5

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

Given the lack of annotations and output schema, the description is incomplete. It doesn't explain what 'connection status' entails (e.g., online/offline, last seen), the return format, or error conditions. For a tool with no structured behavioral data, this leaves critical gaps.

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?

The schema description coverage is 100%, with the parameter 'instanceName' fully documented in the schema. The description doesn't add any additional meaning or context about the parameter beyond what the schema provides, so it meets the baseline for high schema coverage.

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 action ('Get') and resource ('connection status of an instance'), making the purpose immediately understandable. However, it doesn't differentiate from sibling tools like 'connect_instance' or 'list_instances' beyond the basic function, which prevents 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?

No guidance is provided on when to use this tool versus alternatives like 'connect_instance' or 'list_instances'. The description only states what it does, not the context or prerequisites for its use, leaving the agent to infer usage scenarios.

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

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