Phone Carrier Detector MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| detect_carrierC | Detect carrier and location for a single phone number |
| batch_detect_carriersC | Detect carriers and locations for multiple phone numbers |
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 2 tools
The two tools have clearly distinct purposes: one handles single phone numbers and the other handles batches of phone numbers. There is no overlap or ambiguity between them, as the descriptions explicitly differentiate between single and multiple inputs.
Both tools follow a consistent verb_noun pattern with 'detect_carrier' as the base, extended to 'batch_detect_carriers' for the plural/multiple version. The naming is predictable and adheres to snake_case throughout.
With only 2 tools, the server feels thin for a carrier detection domain, as it lacks additional operations like validation, formatting, or carrier metadata lookup. However, the core functionality is covered, making it borderline but not severely lacking.
The server provides basic detection for single and batch inputs, but there are notable gaps such as phone number validation, carrier information retrieval (e.g., network types), or error handling tools. The surface is functional but incomplete for broader carrier-related tasks.