Twilio SMS Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PORT | No | Server Configuration port (Optional, defaults to 3000) | 3000 |
| AUTH_TOKEN | Yes | Your Twilio Auth Token | |
| ACCOUNT_SID | Yes | Your Twilio Account SID, typically starting with 'AC' | |
| FROM_NUMBER | Yes | Your Twilio phone number in E.164 format (e.g., +1234567890) |
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 | {} |
| prompts | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| send-messageC | Send an SMS message via Twilio |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| send-greeting | |
| send-haiku |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 1 tool
With only one tool, there is no possibility of ambiguity or overlap between tools. The single tool 'send-message' has a clear and distinct purpose for sending SMS messages via Twilio.
The single tool name 'send-message' follows a clear verb_noun pattern (send + message). Since there is only one tool, consistency is inherently perfect with no deviations or mixed conventions.
One tool is too few for a server named 'Twilio SMS Server', which suggests a broader SMS functionality scope. Twilio's API typically supports operations like listing messages, checking delivery status, or managing phone numbers, making a single send tool feel incomplete and thin for the domain.
The tool surface is severely incomplete for an SMS server. While sending messages is a core function, there are obvious gaps such as retrieving sent messages, checking message status, or managing SMS-related resources, which are essential for typical SMS workflows and could cause agent failures.