smsmanager
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SMSMANAGER_API_KEY | Yes | Your API key from SmsManager admin panel |
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": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| send_smsA | Send an SMS message to a phone number via SmsManager.cz. Phone numbers should include country code without + (e.g. 420777123456 for Czech). Max 1000 characters. Returns message_id for reference. |
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 confusion or overlap. The single tool has a clear and specific purpose: sending an SMS.
The tool name 'send_sms' follows a clear verb_noun convention and matches its function. With only one tool, there are no inconsistencies to evaluate.
The server has only one tool, which feels thin for the scope implied by 'smsmanager'. A typical SMS manager would reasonably include more than just sending, such as checking message status or account balance.
The tool surface is severely limited to sending SMS. Missing capabilities like viewing sent messages, checking delivery status, or managing contacts leave obvious gaps for an SMS management server.