broker_search
Tool call template
This tool declares no required parameters. Add optional parameters from the input schema as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {},
"name": "broker_search"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| page | No | Page number for paginated results (starts from 1). Use for navigating large datasets when searching broad time periods or popular collectors. | |
| ts_end | No | End timestamp for data collection period. Same format as ts_start. Combine with ts_start to define a specific time window for targeted BGP event analysis or research. | |
| project | No | BGP data collection project. Options: 'routeviews' (University of Oregon RouteViews project) or 'riperis' (RIPE NCC Routing Information Service). Each has different collector locations and methodologies. | |
| ts_start | No | Start timestamp for data collection period. Accepts ISO 8601 format (e.g., '2024-08-01T00:00:00Z') or Unix timestamp. Use to find data from a specific date onwards for historical analysis. | |
| data_type | No | Type of BGP data to retrieve. 'rib' = Routing Information Base (periodic full routing table snapshots, typically every 2-8 hours, ideal for network topology analysis). 'updates' = real-time BGP routing updates (announcements/withdrawals, ideal for studying routing dynamics and outages). | |
| page_size | No | Results per page. Range: 1-1000, default: 100. Use larger values (500-1000) for bulk data discovery, smaller values (10-50) for quick exploration. | |
| collector_id | No | Specific route collector identifier. Examples: 'route-views.linx' (RouteViews LINX), 'rrc01' (Amsterdam). |