Bulk WhatsApp Validator
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| HOST | No | Host configuration (Not applicable) | |
| PORT | No | Port configuration (Not applicable) | |
| API_KEY | Yes | API 密钥 (API Key) for Bulk Whatsapp Validator |
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 |
|---|---|
| tasks | {
"list": {},
"cancel": {},
"requests": {
"tools": {
"call": {}
},
"prompts": {
"get": {}
},
"resources": {
"read": {}
}
}
} |
| tools | {
"listChanged": true
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| is_a_businessC | Requests to this endpoint will return |
| validate_up_to_10B | Enter an array of up to 10 numbers to validate. |
| validate_up_to_100C | Enter an array of up to 100 numbers to validate. |
| validate_single_whatsapp_numberB | Enter a single phone number you want to validate. |
| about_infoC | This endpoint will return the About state of the WA number on the query. |
| validate_up_to_1000C | Enter an array of up to 1000 numbers to validate. |
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 6 tools
Multiple tools have overlapping purposes that could cause confusion. The three validation tools (validate_single_whatsapp_number, validate_up_to_10, validate_up_to_100, validate_up_to_1000) all perform the same core validation function with only batch size differences, while about_info and is_a_business provide distinct metadata. An agent might struggle to choose between the validation tools for a single number, or might use multiple when one would suffice.
The naming conventions are mixed but still readable. The validation tools follow a consistent 'validate_' prefix with descriptive suffixes, while about_info and is_a_business use different patterns (noun_verb vs. question_format). There's no single consistent pattern across all tools, but the names are generally clear and descriptive.
With 6 tools, the count is reasonable but feels inefficiently structured. The server's purpose is WhatsApp number validation and metadata retrieval, but having four separate validation tools for different batch sizes creates redundancy. A more streamlined approach with parameters for batch size would be more appropriate, making the current count feel borderline heavy for the scope.
The tool surface covers the core functionality well for WhatsApp number validation and basic metadata. It provides validation at different scales and returns business status and about information. The main gap is the lack of a unified validation tool with batch size as a parameter, but agents can work around this by selecting the appropriate batch tool. No major missing operations are apparent for the stated purpose.