Skip to main content
Glama
GrizzlySMS-Git

Grizzly SMS MCP Server

Official

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
GRIZZLY_SMS_API_KEYYesYour Grizzly SMS API key
GRIZZLY_SMS_BASE_URLNoBase URL for Grizzly SMS APIhttps://api.grizzlysms.com

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
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
get_balanceB

Get account balance

get_walletA

Get USDT TRC-20 crypto wallet address for balance top-up. Send USDT to this address (min 50 USD). Funds credit automatically.

request_numberB

Request a phone number for SMS verification

set_statusC

Change activation status

get_statusC

Get activation status and SMS code

get_pricesB

Get prices for services by country

get_countriesB

Get list of available countries

get_servicesB

Get list of available services

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.7/5.0

Scored across 8 tools

Disambiguation5/5

Each tool targets a distinct aspect of the SMS verification workflow: account finances, number requests, status management, and reference data. There is no meaningful overlap between any pair of tools.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern in snake_case (e.g., get_balance, request_number). The naming is uniform and predictable across the entire set.

Tool Count5/5

With 8 tools, the server is well-scoped for an SMS verification service. Every tool serves a clear function without unnecessary bloat or missing essentials.

Completeness5/5

The tools cover the core lifecycle: top-up (get_wallet, get_balance), request a number (request_number), poll for SMS (get_status, set_status), and reference data (get_prices, get_countries, get_services). This appears sufficient for the stated purpose.

Maintenance

ActivityInactive
ResponsivenessNo issues