thaibulksms
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| THAIBULKSMS_API_KEY | Yes | API key for SMS and Email (from ThaiBulkSMS dashboard) | |
| THAIBULKSMS_OTP_KEY | No | OTP key for SMS OTP (from OTP Manager) | |
| THAIBULKSMS_API_SECRET | Yes | API secret for SMS and Email (from ThaiBulkSMS dashboard) | |
| THAIBULKSMS_OTP_SECRET | No | OTP secret for SMS OTP (from OTP Manager) |
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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| send_smsA | Send a single SMS via ThaiBulkSMS. Requires user confirmation before sending. |
| check_sms_creditA | Check remaining SMS credit balance on ThaiBulkSMS. |
| send_emailA | Send email via ThaiBulkMail using a template. Requires user confirmation. |
| check_email_creditA | Check remaining email credit balance on ThaiBulkMail. |
| request_otpA | Request an OTP code via SMS to a Thai mobile number. |
| verify_otpA | Verify an OTP PIN against a token from a previous request_otp call. |
| request_email_otpA | Send an OTP code via email using a ThaiBulkMail OTP template. |
| verify_email_otpA | Verify an email OTP code against a token from a previous request_email_otp call. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 8 tools
Each tool targets a distinct action and resource: sending SMS, checking credits, and OTP flows are clearly separated. Even send_sms vs request_otp are distinguishable by purpose, with descriptions clarifying the OTP-specific nature.
All tools follow a consistent verb_noun pattern in snake_case, such as send_sms, check_sms_credit, request_otp, and verify_email_otp. The naming is uniform and predictable.
With 8 tools, the server is well-scoped, covering SMS and email sending, credit checks, and OTP verification. This is within the ideal range for a focused API integration.
The server covers core operations for SMS and email, including send, credit check, and OTP flows. However, given the 'bulk' in the server name, a bulk send operation is missing, though single operations are adequately covered.