Dispatchers already ask AI assistants everything: draft the broker email, explain the detention clause, convert the rate to per-mile. Ask one what is closed on tonight’s lane and it will apologise. A language model knows roads the way an atlas does. It has never seen tonight’s lane closure, a posted bridge, or how many spaces the welcome center has.
It can, if something feeds it. We connected an assistant to the Road511 API through our remote MCP server and asked it the question a dispatcher would ask on a Saturday afternoon. Below is what it did and what it answered, as of 14 November 2026, 17:40 UTC. Nothing is staged: the tool calls went to the production API, the same as any customer’s.
The Question
I'm a dispatcher. Tonight I have a 53' dry van leaving Atlanta, GA
(Fulton Industrial Blvd area) at 21:00 local for Nashville, TN.
Truck is 13'6" tall, 80,000 lb gross, 5 axles, no hazmat.
1. What is closed, under construction or otherwise in the way tonight?
2. Anything about clearance or weight I should worry about?
3. The driver will want a break around Chattanooga roughly 1 a.m.
Where can he park, and do we know if it fills up?
Say plainly when the data does not tell you something.
What the Assistant Did
It made six calls before answering. Nobody told it which ones to make.
| Tool | What it asked for |
|---|---|
plan_truck_route | Atlanta → Nashville for a 36.3 t, 4.11 m, 5-axle truck, departing 21:00 Eastern. The route comes back with every hazard on it, each with the time the truck reaches it. |
search_events | Active incidents in a box around the corridor. |
search_features ×3 | Truck parking and rest areas within 50 km of Chattanooga; weigh stations on the corridor. |
list_feature_types | What else exists, to check it had not missed a data type. |
The route call does most of the work. One request returns the road the truck takes and 34 warnings along it: lane closures and construction with their validity windows, posted bridges compared against the truck’s weight, rail crossings with the railroad’s emergency number, road-weather readings from the stations it passes. Each warning carries its distance along the route and a projected arrival time. “Is this still active when he gets there” becomes a lookup, not a guess.
What It Answered
Before anything else, it corrected the plan:
“Your timing doesn’t work as planned. The route is I-285 → I-75 N → I-24 W, 249 mi, about 4 h 11 min of driving with no stops. Leaving at 21:00 ET, the driver reaches Chattanooga around 22:55 ET and Nashville around 00:11 CT. At 1 a.m. he would be about 10 minutes from Nashville, not near Chattanooga.”
Then the closures, in the order the truck reaches them:
| Reached (est.) | Where | What |
|---|---|---|
| 21:11 ET | I-75 NB at Windy Hill Rd | Construction, four left lanes blocked until Monday 05:00 |
| ~23:15 ET | I-24, Marion Co., MM 134–160 | Rolling roadblocks for marker work through 30 November; the feed gives no hours |
| ~22:59 CT | I-24, Coffee Co., MM 116.8–117.6 | Bridge replacement, nightly 7 PM–6 AM, traffic diverted over the Exit 117 ramps with a 12 ft width limit |
| ~23:47 CT | I-24 WB, Rutherford Co., MM 71.2–66 | Lane closures for bridge-joint repair, one lane always open |
The Coffee County entry is the one to read twice. The state’s own text says the eastbound diversion “will shift to I-24 WB with similar closures”, and the assistant named exactly what that leaves open: “The data doesn’t say whether westbound has started yet.” That is a phone call to make before 21:00, and now somebody knows to make it.
It also caught something no map pin shows. The route ends in downtown Nashville, and among its warnings on the last mile is the Woodland Street Bridge over the Cumberland, which the federal bridge inventory lists as posted at 17.2 tonnes (about 37,900 lb). The route flags it as not confirmed on the truck’s road, and says so; the dispatcher still gets to see it. The assistant’s advice: keep the final leg off it at 80,000 lb, and send the real consignee address so the route can be re-run to the dock instead of a city centre.
What It Said It Did Not Know
This part makes the case better than the closures do. Asked whether the parking near Chattanooga fills up, it did not guess:
“Nothing tells you whether they fill up. For all of them road511 has only static capacity. There is no live occupancy feed for GA or TN here, and commercial truck stops didn’t come up in this search.”
It then listed the three lots on the driver’s side of the road (35, 13 and 14 truck spaces) and put the lots on the opposite carriageway in a separate “wrong side” list. Every time the data ran out, it said so. The road-weather readings are midday observations, not a forecast for the run. The morning’s disabled-vehicle incidents will be stale by 21:00. The rolling-roadblock event publishes no hours. An assistant that says “I don’t know, here is who does” is one a dispatcher can trust with the parts it does know.
What Writing This Post Fixed
The first run of this conversation, earlier the same day, was not this clean. The assistant answered well, but only by explaining away four kinds of warning our route should never have raised:
- a 6′8″ height limit that turned out to be the gate of a convention-centre parking garage, mapped in OpenStreetMap;
- a 0.6 t “weight limit” on I-24 over Missionary Ridge: an inspection rating of a bridge that is shored and open to all traffic;
- clearance and weight warnings from the eastbound twins of bridges the westbound truck crosses;
- weight warnings for bridges on side roads a few dozen metres from the interstate.
All four were fixed and deployed the same day. Garage and car-park limits are no longer imported. A shored bridge counts as open. A twin structure is matched to the carriageway the route actually drives. A side-road bridge no longer warns a truck on the interstate beside it. The answers quoted above come from the second run, on the fixed API. One leftover shows in the transcript: the garage gate’s old record stays until the next full OpenStreetMap refresh, so the assistant still had to call it noise.
Connecting Your Own Assistant
One line for Claude Code; any MCP client takes the same URL and header.
claude mcp add --transport http road511 https://api.road511.com/api/v1/mcp \
--header "Authorization: Bearer YOUR_API_KEY"
The server uses your normal API key and your plan. Each tool call is one API request with the same rate limits and plan gates as a direct call, and plan_truck_route counts against your plan’s monthly routing quota.
What This Is Not
- It is not a dispatcher. The assistant reads the same data your planners would. It is fast and it does not skip a feed, but it does not know the customer, the driver’s hours or the dock.
- It is only as live as the feeds. Closures and incidents are what the state 511 systems publish, when they publish it. A closure nobody has entered is not in the answer.
- Absent is unknown. No warning on a stretch means no record, not a clear road. The assistant said so where it mattered.
- Re-ask close to departure. Everything quoted here is a reading at one moment on 14 November. Ask again at 20:30.
Try It
- MCP setup — the server URL, headers and the tool list.
- Humped rail crossings and the ENS sign — one of the warning types the route carries.
- Free trial API key — no credit card.
Give the assistant the road, not just the map
Truck-aware routing with live closures, posted bridges, clearances, rail crossings and parking, as API calls or as tools for your AI assistant.
Get an API key Set up MCP