mcp-whatsms-admin
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| WHATSMS_API_URL | No | The URL of the WhatSMS Admin API | https://whatsms.descomplicar.pt/admin |
| WHATSMS_API_TOKEN | Yes | Your WhatSMS Admin API token (required, system level privileges) |
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 | {} |
| prompts | {} |
| resources | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| whatsms_admin_get_usersA | List all users in the WhatSMS system with optional pagination |
| whatsms_admin_create_userC | Create a new user in the WhatSMS system |
| whatsms_admin_update_userA | Update an existing user in the WhatSMS system |
| whatsms_admin_delete_userB | Delete a user from the WhatSMS system |
| whatsms_admin_get_rolesA | List all roles/functions in the WhatSMS system with optional pagination |
| whatsms_admin_create_roleB | Create a new role/function in the WhatSMS system |
| whatsms_admin_update_roleB | Update an existing role/function in the WhatSMS system |
| whatsms_admin_delete_roleB | Delete a role/function from the WhatSMS system |
| whatsms_admin_get_packagesA | List all packages in the WhatSMS system with optional pagination |
| whatsms_admin_create_packageB | Create a new package in the WhatSMS system |
| whatsms_admin_update_packageB | Update an existing package in the WhatSMS system |
| whatsms_admin_delete_packageB | Delete a package from the WhatSMS system |
| whatsms_admin_get_subscriptionsA | List all subscriptions in the WhatSMS system with optional pagination |
| whatsms_admin_create_subscriptionB | Create a new subscription in the WhatSMS system |
| whatsms_admin_delete_subscriptionB | Delete a subscription from the WhatSMS system |
| whatsms_admin_get_transactionsA | List all transactions in the WhatSMS system with optional pagination and filtering |
| whatsms_admin_delete_transactionB | Delete a transaction from the WhatSMS system |
| whatsms_admin_get_vouchersA | List all vouchers in the WhatSMS system with optional pagination |
| whatsms_admin_create_voucherB | Create a new voucher in the WhatSMS system |
| whatsms_admin_redeem_voucherB | Redeem a voucher for a user in the WhatSMS system |
| whatsms_admin_delete_voucherB | Delete a voucher from the WhatSMS system |
| whatsms_admin_get_apikeysA | List all API keys in the WhatSMS system with optional pagination |
| whatsms_admin_create_apikeyA | Create a new API key for a user in the WhatSMS system |
| whatsms_admin_delete_apikeyB | Delete an API key from the WhatSMS system |
| whatsms_admin_clear_cacheB | Clear the system cache |
| whatsms_admin_get_languagesA | Get all available languages from the WhatSMS platform |
| whatsms_admin_health_checkA | Perform comprehensive system health check with performance metrics |
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 27 tools
Each tool names a specific resource and action (e.g., users, roles, packages), making their purposes distinct. Even similar operations differ by target resource, so an agent can easily select the right tool.
All tools follow a strict `whatsms_admin_` prefix with snake_case verb_noun (e.g., `create_user`, `delete_voucher`), ensuring a predictable and consistent pattern.
At 27 tools, the set is large, but it covers seven distinct entities plus system operations (cache, languages, health). It's borderline heavy but each tool addresses a separate administrative need.
The CRUD coverage is solid for primary entities, with minor omissions like no update for subscriptions, no get-by-id endpoints, and transactions only supporting get/delete. These are workable gaps but not fatal.