I-5 conditions now
dogpolicies_i5_conditionsIs I-5 open right now: lane closures, chain controls, road weather and sign messages on the freeway in California, and the nearest dog stop to each? Live state, not rules: Caltrans feeds fetched within the last 15 minutes (fetched_at in the result), not verified rules. Covers the Grapevine and every other stretch of I-5 in California. Other highways are not covered. Inputs: from_mile and to_mile, or near={lat, lon} with direction and ahead_miles; with none, all of I-5 in California. Each condition is placed on the I-5 centerline (mile, s meters from San Ysidro) and matched to the nearest dog stop. If the feeds cannot be read the answer has outcome unavailable and the address of the live Caltrans page. A result older than two hours is marked stale.
Examples:
"Is there a closure or chains on the Grapevine right now?" -> from_mile=170, to_mile=222
"Weather and closures in the next 60 miles northbound from Redding" -> near={lat:40.59, lon:-122.39}, direction="north", ahead_miles=60
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": "dogpolicies_i5_conditions"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| near | No | A point on or near I-5 | |
| to_mile | No | End of a mile range | |
| direction | No | Direction of travel from near | north |
| from_mile | No | Start of a mile range | |
| ahead_miles | No | Window in miles from near | |
| response_format | No | 'markdown' for readable text, 'json' for structured data | markdown |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| code | No | With an outcome other than ok: not_found, invalid, unavailable | |
| next | No | Calls that would answer the question, in words | |
| as_of | Yes | Date the data was built (YYYY-MM-DD) | |
| signs | Yes | ||
| stale | No | True when the document is older than two hours | |
| notice | Yes | ||
| source | Yes | ||
| window | Yes | ||
| license | Yes | ||
| message | No | What happened, in a sentence | |
| nearest | No | When nothing is inside the radius: the nearest places in the data, with distance_miles | |
| outcome | No | Absent or ok: a normal answer. no_match: nothing in the data matches, see did_you_mean, nearest and next. bad_input: the arguments cannot be used as given, see next. partial: some of the ids were found, see missing. unavailable: a live source could not be read. None of these is an error. | |
| weather | Yes | ||
| accepted | No | With bad_input: each argument that could not be read, with the values it accepts | |
| closures | Yes | ||
| fetched_at | Yes | When the loop fetched the feeds; null when no document could be read | |
| nearest_i5 | No | With a point too far from I-5: the nearest point on I-5 and how far it is | |
| did_you_mean | No | Close matches to what was asked for: towns, places, slugs or brands, best first | |
| resolved_from | No | Set when a word was read as the value the tool uses: hotel as lodging, NB as north. Each key is the argument; asked is what was sent, used what it was read as | |
| chain_controls | Yes | ||
| attribution_url | Yes | ||
| attribution_text | Yes | ||
| chains_in_effect | Yes |