Skip to main content
Glama
J-Gal02

ClickSend MCP Server

by J-Gal02

send_sms

Send SMS messages to phone numbers using ClickSend's API. This tool enables programmatic SMS delivery with built-in rate limiting and input validation for reliable communication.

Instructions

Send SMS messages via ClickSend

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
toYesPhone number in E.164 format (e.g. +61423456789)
messageYesMessage content to send

Implementation Reference

  • The core handler function in ClickSendClient that executes the SMS sending logic via the ClickSend API, including payload construction and error handling.
    async sendSMS(params: SMSMessage) {
      const payload = {
        messages: [
          {
            source: 'mcp',
            body: params.message,
            to: params.to
          }
        ]
      };
    
      try {
        const response = await this.client.post('/sms/send', payload);
        return response.data;
      } catch (error) {
        if (axios.isAxiosError(error)) {
          throw new Error(`ClickSend API Error: ${error.response?.data?.message || error.message}`);
        }
        throw error;
      }
    }
  • src/index.ts:65-82 (registration)
    Registration of the 'send_sms' tool in the ListTools handler, including name, description, and input schema.
      name: 'send_sms',
      description: 'Send SMS messages via ClickSend',
      inputSchema: {
        type: 'object',
        properties: {
          to: {
            type: 'string',
            description: 'Phone number in E.164 format (e.g. +61423456789)'
          },
          message: {
            type: 'string',
            description: 'Message content to send'
          }
        },
        required: ['to', 'message'],
        additionalProperties: false
      }
    },
  • Server-side dispatch handler for 'send_sms' tool calls, including validation and delegation to client.sendSMS.
    case 'send_sms': {
      const { to, message } = request.params.arguments as { to: string; message: string };
      validateSMSParams(to, message);
      const result = await this.client.sendSMS({ to, message });
      return {
        content: [
          {
            type: 'text',
            text: `SMS sent successfully: ${JSON.stringify(result)}`
          }
        ]
      };
    }
  • TypeScript interface defining the input parameters for sendSMS.
    export interface SMSMessage {
      to: string;
      message: string;
    }
  • Validation helper function for SMS parameters used in the tool handler.
    export function validateSMSParams(to: string, message: string): void {
      if (!validatePhoneNumber(to)) {
        throw new ValidationError('Invalid phone number format. Must be in E.164 format (e.g., +61423456789)');
      }
      if (!validateMessage(message)) {
        throw new ValidationError('Invalid message. Must be between 1 and 1600 characters');
      }
    }
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. While 'Send SMS messages' implies a write/mutation operation, it doesn't disclose important behavioral traits like authentication requirements, rate limits, cost implications, delivery confirmation, or error handling. The description is minimal and lacks operational context.

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 4 words, front-loading the essential information with zero wasted words. Every word earns its place in communicating the core functionality.

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?

For a mutation tool with no annotations and no output schema, the description is insufficiently complete. It doesn't address what happens after sending (success/failure responses), doesn't mention the sibling tool relationship, and provides minimal operational context for a tool that presumably has costs, authentication needs, and delivery considerations.

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 both parameters ('to' and 'message') well-documented in the schema itself. The description adds no additional parameter information beyond what's already in the structured schema, so it meets the baseline for high schema coverage without adding extra value.

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 ('Send SMS messages') and the target resource ('via ClickSend'), providing a specific verb+resource combination. However, it doesn't differentiate from the sibling tool 'make_tts_call' which appears to be a different communication method (text-to-speech call).

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 the sibling tool 'make_tts_call' or any contextual factors that would help an agent choose between SMS and TTS communication methods.

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/J-Gal02/clicksend-mcp'

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