sms-web2sms-mcp-server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PORT | No | Server port (default: 3000). | 3000 |
| WEB2SMS_SECRET | No | API secret from web2sms.ro dashboard. Required if not provided per-request. | |
| WEB2SMS_SENDER | No | Default sender ID. | |
| WEB2SMS_API_KEY | No | API key from web2sms.ro dashboard. Required if not provided per-request. |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| send_smsB | Send an SMS message via web2sms.ro Romanian SMS gateway |
| check_statusB | Check SMS delivery status via web2sms.ro SOAP API |
| check_balanceA | Check prepaid SMS credit balance on web2sms.ro |
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 3 tools
Each tool targets a distinct operation: sending, status checking, and balance checking. There is no overlap in purpose, making selection unambiguous.
All tool names follow a consistent verb_noun pattern: send_sms, check_status, check_balance. This is predictable and easy to understand.
With 3 tools, the server is well-scoped for its stated purpose of SMS management. Each tool is essential and the count fits within the ideal 3-15 range.
The core lifecycle of sending an SMS and tracking it is covered: send, check status, and check balance. A minor gap is lack of additional management features like message history, but these three operations are sufficient for the primary use case.