Skip to main content
Glama
luiso2

Evolution API WhatsApp MCP Server

by luiso2

send_text

Send WhatsApp messages using Evolution API, including predefined templates for business communications like order confirmations and appointment reminders.

Instructions

Send a text message

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
delayNoDelay in milliseconds
instanceNameYesInstance name
numberYesRecipient phone number
textYesMessage text

Implementation Reference

  • MCP tool handler for 'send_text': extracts arguments, calls evolutionAPI.sendText, formats and returns the result as MCP content.
    private async handleSendText(args: any) {
      const result = await evolutionAPI.sendText(args.instanceName, {
        number: args.number,
        text: args.text,
        delay: args.delay
      });
      return {
        content: [
          {
            type: 'text',
            text: JSON.stringify(result, null, 2)
          }
        ]
      };
    }
  • Tool definition including name, description, and input schema for validation.
    {
      name: 'send_text',
      description: 'Send a text message',
      inputSchema: {
        type: 'object',
        properties: {
          instanceName: { type: 'string', description: 'Instance name' },
          number: { type: 'string', description: 'Recipient phone number' },
          text: { type: 'string', description: 'Message text' },
          delay: { type: 'number', description: 'Delay in milliseconds' }
        },
        required: ['instanceName', 'number', 'text']
      }
    },
  • src/index.ts:498-499 (registration)
    Registration in the tool dispatch switch statement within CallToolRequestSchema handler.
    case 'send_text':
      return await this.handleSendText(args);
  • Helper method in EvolutionAPI service that sends HTTP POST request to the underlying Evolution API endpoint for sending text messages.
    async sendText(instanceName: string, data: {
      number: string;
      text: string;
      delay?: number;
      linkPreview?: boolean;
    }): Promise<Message> {
      const response = await this.client.post(`/message/sendText/${instanceName}`, data);
      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 full burden for behavioral disclosure. 'Send a text message' implies a write operation but doesn't address permissions, rate limits, side effects, error conditions, or what happens on success. For a mutation tool with zero annotation coverage, this is inadequate.

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 extremely concise at just three words, front-loading the core purpose with zero wasted language. Every word earns its place, making it efficient for quick scanning.

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 this is a mutation tool with no annotations, no output schema, and multiple sibling alternatives, the description is incomplete. It doesn't explain what the tool returns, how it differs from other send_* tools, or any behavioral constraints. The agent would need to guess about important operational aspects.

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?

Schema description coverage is 100%, with all parameters documented in the schema. The description adds no additional parameter information beyond what's already in the structured fields. According to scoring rules, when schema coverage is high (>80%), the baseline is 3 even with no param info in the description.

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 'Send a text message' clearly states the verb ('send') and resource ('text message'), making the purpose immediately understandable. However, it doesn't differentiate from sibling tools like send_buttons, send_list, send_media, or send_template, which all involve sending different types of messages through the same system.

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 like send_buttons, send_list, send_media, or send_template. There's no mention of prerequisites, context, or exclusions, leaving the agent to infer usage from tool names alone.

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