Skip to main content
Glama
TopSMS MCP server

TopSMS MCP server

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
TOPSMS_SECRETYesYour TopSMS API Secret, created in the dashboard under API klíče with scopes send and read.
TOPSMS_CLIENT_IDYesYour TopSMS API Client ID, created in the dashboard under API klíče with scopes send and read.

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

CapabilityDetails
tools
{
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
send_smsA

Send one SMS message via the TopSMS SMS gateway (topsms.eu / topsms.cz). Costs credit: 160 GSM-7 chars = 1 SMS, 70 with other diacritics/emoji. Returns message id, number of segments and price in your account currency (field currency: EUR for topsms.eu accounts, CZK for topsms.cz).

send_bulk_smsA

Send the same SMS text to up to 500 recipients. Batches over 50 recipients are queued (HTTP 202) and return a jobId; use get_bulk_job to follow progress.

get_message_statusA

Get delivery status of a sent message (queued, sent, delivered, failed, expired) with timestamps, errorMessage and machine-readable errorCode (expired, undelivered, rejected, deleted, unknown, repeated_failure, not_sent), by message id or external id.

get_bulk_jobA

Get progress of a queued bulk send (status, sent, failed, queued counts and per-message results).

cancel_scheduledA

Cancel a scheduled send (or a queued bulk job that has not started yet). Unsent messages are removed and their price is returned to credit.

verify_sendA

Send a one-time verification code (OTP) by SMS for login, registration or payment confirmation. TopSMS generates and stores the code; returns a verification id. Limits: 5 codes per number per hour, 30 s between codes.

verify_checkA

Check a verification code the user entered. Returns valid true/false, status (approved, pending, expired, failed, canceled) and attempts left (max 5 attempts per code).

get_creditA

Get the current TopSMS credit balance and the price per SMS, both in your account currency (field currency: EUR for topsms.eu accounts, CZK for topsms.cz accounts).

get_pricingA

Get the current public TopSMS price list (prices per destination zone, volume tiers, sender name fee, billing rules). Does not require credentials. Use it instead of quoting prices from memory.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.9/5.0

Scored across 9 tools

Disambiguation5/5

Each tool targets a distinct resource+action pair: single send vs bulk send, single message status vs bulk job progress, verify_send vs verify_check, and balance vs price list. The only near-neighbours (get_credit / get_pricing) are explicitly differentiated in their descriptions as balance vs public price list. No two tools appear interchangeable.

Naming Consistency4/5

All names are snake_case and verb-first, with a clear verb+object shape (send_sms, get_message_status, get_bulk_job, get_credit). Minor deviations exist: cancel_scheduled has an adjectival object with no resource noun, and verify_send/verify_check use a verb+verb form rather than verb+noun. Still highly predictable overall.

Tool Count5/5

Nine tools is well-scoped for an SMS gateway: sending (single/bulk), tracking (single/bulk), cancellation, OTP verification, and account lookup. Each tool covers a distinct capability with no filler or redundant wrappers.

Completeness3/5

The core send/track/verify/credit surface is covered, but cancel_scheduled is orphaned — there is no tool to schedule a send or bulk job in the first place, so that capability is a dead end. Other notable gaps: no tool to list message history or inbound/received messages, and sender-name configuration is only mentioned in pricing.

Maintenance

ActivityMaintained
ResponsivenessNo recent community issues