route-comms-link
Route communication to optimal link based on range, data rate, criticality, and link availability. 7 link types: BLE (controller), Wi-Fi 6E (ground station), 5G (cloud), LoRa (telemetry fallback), Iridium Certus (satcom), VHF radio (ATC), ADS-B Out (position broadcast).
Taxonomy
Linnaean classification joined from the algovigilance taxonomy index via the parent config's rank.
| Rank | Value |
|---|---|
| domain | Substrata |
| kingdom | Constructa |
| phylum | Configa |
| class | station-config |
| order | comms |
| family | mcp-tool-config |
Characteristics:
- substrate:
config - domain:
pv - lifecycle:
continuous - authority:
read - compounding:
producer - io:
agent-request→tool-response
Input schema
range_kmnumberrequired — Distance to destination in kilometersdata_rate_requiredstringrequired — Required throughput: telemetry_only, low_bandwidth, medium_bandwidth, high_bandwidth, videocriticalitystring — Message criticality: routine, priority, emergency, atc_mandatoryairborneboolean — Whether the suit is currently in flightprimary_5g_statusstring — 5G modem state: connected, weak, unavailablewifi_availableboolean — Whether Wi-Fi 6E ground station is in range
Example call
POST /api/mcp
Content-Type: application/json
{
"jsonrpc": "2.0",
"id": 1,
"method": "tools/call",
"params": {
"name": "station__comms-systems__route-comms-link",
"arguments": {
"range_km": 0,
"data_rate_required": ""
}
}
}How to invoke from a client
From any MCP-aware client, add https://algovigilance.com/api/mcp as an MCP server, then call this tool by name. From a raw HTTP client, send the JSON-RPC body above to /api/mcp.
Agent-friendly formats
Working inside an AI assistant? Use the Copy for AI button at the top of this page (or view the raw Markdown) to paste a clean, token-budgeted version of this tool's contract into your conversation.
Related
- All tools (3062 live)
- /api/mcp — endpoint
- /AGENTS.md — agent guide
- /tools/comms-systems__route-comms-link/raw.md — this page's Markdown twin