bach-whatsapp_number_validators
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| HOST | No | 主机地址（不适用） | |
| PORT | No | 端口号（不适用） | |
| API_KEY | Yes | API 密钥 |
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
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| pingC | Ping Validation Test |
| check_if_number_is_business_via_get_requestB | Verify whether a given number is registered on WhatsApp and determine if it belongs to WhatsApp Business. To obtain the status of a particular number, please provide the number along with the corresponding country code. |
| check_if_number_is_business_via_post_requestC | Verify whether a given number is registered on WhatsApp and determine if it belongs to WhatsApp Business. To obtain the status of a particular number, please provide the number along with the corresponding country code. |
| bulk_validationA | Verify up to 25 numbers in once call. For each number, verify whether this number is registered on WhatsApp and determine if it belongs to WhatsApp Business. To obtain the status of these numbers, please provide all numbers along with the corresponding country code. |
| validate_single_number_via_get_requestB | Verify whether a given number is registered on WhatsApp and determine if it belongs to WhatsApp Business. To obtain the status of a particular number, please provide the number along with the corresponding country code. |
| validate_single_number_via_post_requestB | Verify whether a given number is registered on WhatsApp and determine if it belongs to WhatsApp Business. To obtain the status of a particular number, please provide the number along with the corresponding country code. |
| phone_number_validation_via_get_requestC | You can utilize a phone number validator to verify the validity of a given number. In case the number is invalid, the validator will provide alternative valid phone numbers for different countries associated with the given number. |
| phone_number_validation_via_post_requestC | You can utilize a phone number validator to verify the validity of a given number. In case the number is invalid, the validator will provide alternative valid phone numbers for different countries associated with the given number. |
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 8 tools
Multiple tools have overlapping purposes with unclear boundaries. For example, check_if_number_is_business_via_get_request, check_if_number_is_business_via_post_request, validate_single_number_via_get_request, and validate_single_number_via_post_request all appear to perform the same WhatsApp Business verification, differing only by HTTP method. This creates significant ambiguity and potential for misselection by an agent.
Naming conventions are inconsistent and chaotic. Tools mix descriptive names (bulk_validation, phone_number_validation_via_get_request) with vague ones (ping), and there is no consistent pattern. Some tools use snake_case with HTTP method suffixes, while others do not, leading to a lack of predictability across the set.
With 8 tools, the count is reasonable for a validation server, but it feels borderline due to redundancy. The number of tools is inflated by multiple versions of the same functionality (e.g., GET vs. POST for similar checks), which could have been consolidated, making the set feel slightly heavy for its scope.
The tool set covers the core domain of WhatsApp number validation well, including bulk and single validations, business checks, and general phone number validation. However, there are minor gaps, such as no tools for managing validation results or handling errors explicitly, but agents can likely work around these with the provided tools.