@theyahia/sms-ru-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SMS_RU_API_ID | Yes | Your SMS.RU API ID. Get it from https://sms.ru/my/settings |
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_smsB | Отправить SMS через SMS.RU. Принимает номер (79XXXXXXXXX), текст, опционально имя отправителя. |
| check_statusA | Проверить статус отправленного SMS по его ID. |
| get_balanceB | Проверить баланс аккаунта SMS.RU. |
| get_costA | Рассчитать стоимость SMS до отправки. Принимает номер и текст сообщения. |
| get_sendersA | Получить список одобренных имён отправителей на аккаунте SMS.RU. |
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 5 tools
Each tool has a distinct purpose: sending, status checking, balance, cost calculation, and sender list. No overlap or ambiguity.
All tool names follow a consistent verb_noun pattern in snake_case (send_sms, check_status, get_balance, get_cost, get_senders).
5 tools are well-scoped for an SMS service, covering the essential operations without being overwhelming or sparse.
Covers core SMS lifecycle (send, check, balance, cost, senders) but lacks features like message history or scheduling, which are minor gaps.