46 lines
1.6 KiB
Markdown
46 lines
1.6 KiB
Markdown
---
|
|
description: Search telecom destinations by prefix, country, network, or MCC/MNC
|
|
---
|
|
|
|
# Destinations Search Command
|
|
|
|
You are helping the user search the Destinations API for telecommunications data. Follow these steps:
|
|
|
|
1. **Parse the user's query** to identify:
|
|
- Phone number prefix (e.g., "1", "44", "855")
|
|
- Country name (e.g., "UNITED STATES", "CAMBODIA")
|
|
- Network description (e.g., "Mobile", "Fixed")
|
|
- MCC/MNC code (e.g., 45601)
|
|
|
|
2. **Construct the API request** to `https://destinations-api.telecomsxchange.com/search/` with appropriate query parameters:
|
|
- `prefix` - for phone number prefixes
|
|
- `country_name` - for country searches
|
|
- `description` - for network type searches
|
|
- `mccmnc` - for MCC/MNC lookups
|
|
- `limit` - default to 100, max 1000
|
|
|
|
3. **Use the WebFetch tool** to query the API with a prompt like:
|
|
"Extract and return all destination records with their prefix, country_name, description, mccmnc, interval_1, and interval_n fields in a clear table format"
|
|
|
|
4. **Present the results** in a well-formatted table showing:
|
|
- Prefix
|
|
- Country
|
|
- Network/Operator
|
|
- MCC/MNC
|
|
- Billing (interval_1/interval_n)
|
|
|
|
5. **Explain billing increments** when relevant:
|
|
- 60/60 = 60s minimum, then per-minute
|
|
- 60/1 = 60s minimum, then per-second (better)
|
|
- 1/1 = per-second from start (best)
|
|
|
|
6. **Handle pagination** if results exceed limit - inform user they can specify a page number
|
|
|
|
**Rate Limit:** Remember the API allows 100 requests per minute.
|
|
|
|
**Example queries to handle:**
|
|
- "Search for Cambodia mobile networks"
|
|
- "Find prefix +1"
|
|
- "Look up MCC/MNC 45601"
|
|
- "Show all destinations in United States"
|