Aligo SMS MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
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
| Name | Description |
|---|---|
| send-smsC | Send SMS messages through the Aligo API |
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 1 tool
With only one tool, there is no possibility of ambiguity or overlap between tools. The single tool 'send-sms' has a clear and distinct purpose, making it impossible for an agent to misselect between multiple options.
The single tool name 'send-sms' follows a consistent verb-noun pattern, using kebab-case. Since there is only one tool, there is no inconsistency in naming conventions, and the pattern is straightforward and predictable.
The server has only one tool, which feels thin for an SMS service domain. While it covers the core functionality of sending SMS, typical SMS APIs include additional operations like checking status, managing templates, or retrieving messages, making this set under-scoped for the apparent purpose.
The tool set is severely incomplete for an SMS service. It only provides 'send-sms', lacking essential operations such as checking delivery status, retrieving sent messages, managing contacts, or handling errors, which are common in SMS APIs and necessary for robust agent workflows.