Skip to main content
Glama
TitanmindAGI

Titanmind WhatsApp MCP

by TitanmindAGI

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

No arguments

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Server capabilities have not been inspected yet.

Tools

Functions exposed to the LLM to take actions

NameDescription
get_conversations_from_the_last_dayD
get_the_messages_of_a_conversation_D
send_whatsapp_message_to_a_conversationD
register_msg_template_for_approvalB
creates and registers a new whatsapp message template for approval.
Args:
    template_name (str): name of the whatsapp message template, It only accepts a single word without no special characters except underscores
    language (str): language of the whatsapp message template (default is "en")
    category (str): category of the whatsapp message template (default is "MARKETING"), other possible values are "UTILITY", "AUTHENTICATION"
    message_content_components (dict): the message content that needs to be sent. It needs to be structured like the below example, 
    components are required to have BODY component at least, like this: {"type": "BODY", "text": "lorem body text"}, BODY component is for the simple text.
    All other components are optional. 
    HEADER component can have any of the below format, but only one format at a time can be used.: TEXT(the header component with TEXT needs to be like this
    {
    "type": "HEADER",
    "format": "TEXT",
    "text": "lorem header text"
    }
    ), VIDEO(the header component with VIDEO needs to be like this
    {
     "type":"HEADER",
     "format":"VIDEO",
     "example":{
        "header_handle":[
           "https://sample_video_url.jpg"
        ]
     }
    }
    )
    , IMAGE(the header component with IMAGE needs to be like this 
    {
     "type":"HEADER",
     "format":"IMAGE",
     "example":{
        "header_handle":[
           "https://sample_image_url.jpg"
        ]
     }
    }),
   DOCUMENT (the header component with DOCUMENT needs to be like this 
    {
     "type":"HEADER",
     "format":"DOCUMENT",
     "example":{
        "header_handle":[
           "https://sample_document_url"
        ]
     }
  }),
    message_content_components value with all other type of components is mentioned below.
        [
                {
                    "type": "HEADER",
                    "format": "TEXT",
                    "text": "lorem header text"
                },
                {
                    "type": "BODY",
                    "text": "lorem body text"
                },
                {
                    "type": "FOOTER",
                    "text": "lorem footer text"
                },
                {
                    "type": "BUTTONS",
                    "buttons": [
                        {
                            "type": "QUICK_REPLY",
                            "text": "lorem reply bt"
                        },
                        {
                          "type": "URL",
                          "text": "cta",
                          "url": "https:sample.in"
                        },
                        {
                          "type": "PHONE_NUMBER",
                          "text": "call ",
                          "phone_number": "IN328892398"
                        }
                    ]
                }
            ]
    Buttons need to follow order of first QUICK_REPLY, then URL, and then PHONE_NUMBER.
get_the_templatesD
send_msg_to_multiple_num_using_approved_templateD

Prompts

Interactive templates invoked by user choice

NameDescription
whatsapp_and_server_workflowWhatsApp messaging workflow guide, and server tools return info
send_whatsapp_messageWhatsApp messaging workflow guide, and server tools return info

Resources

Contextual data attached and managed by the client

NameDescription
whatsapp_and_server_workflow_resourceWhatsApp messaging workflow guide, and server tools return info

TDQS

D1.7/5.0

Scored across 6 tools

Disambiguation3/5

The tools have distinct purposes (get conversations, get messages, get templates, register template, send template messages, send direct messages), but some ambiguity exists between 'send_msg_to_multiple_num_using_approved_template' and 'send_whatsapp_message_to_a_conversation' since both involve sending messages. The lack of descriptions for most tools exacerbates this overlap.

Naming Consistency2/5

Naming is inconsistent with mixed conventions: some use snake_case with underscores (e.g., 'get_conversations_from_the_last_day'), others have trailing underscores (e.g., 'get_the_messages_of_a_conversation_'), and verbs vary (e.g., 'get' vs. 'register'). While all names are descriptive, the lack of a uniform pattern reduces predictability.

Tool Count4/5

With 6 tools, the count is reasonable for a WhatsApp-focused server, covering core operations like retrieving conversations/messages/templates, registering templates, and sending messages. It's slightly lean but not overly sparse, allowing for basic functionality without being overwhelming.

Completeness3/5

The server covers key WhatsApp operations (read conversations/messages, manage templates, send messages), but there are notable gaps: no tools for updating or deleting templates, managing conversation participants, or handling message statuses. The surface supports basic workflows but lacks full lifecycle management for templates and conversations.

Maintenance

ActivityInactive
ResponsivenessNo issues