Server definition
- Hash
- sha256:1c43b4363863db7932131a897c652d816fc8f0bb520961062969e2c8be549db3
- What it is
- What a remote MCP server returned when asked what it offers: 10 tools
The blob, as servednamed by its sha256
{
"instructions": "Live road conditions. California in depth: CHP incidents, Caltrans lane\nclosures and chain controls, cameras and message signs, WFIGS wildfires,\nand TomTom traffic on 17 curated corridors. Everywhere else CommuteScout\ncovers (37 US states) through get_nearby_events. All data is official,\npublic, and read-only. Every response carries a `sources` list with a\n`data_as_of` timestamp per source - always relay meaningful staleness or\nfeed errors to the user. This service reports CURRENT conditions only; it\ncannot forecast. Remind users to verify before they drive (dial 511 or check\nquickmap.dot.ca.gov). Not affiliated with any government agency.\n",
"tools": [
{
"description": "Full current-conditions report for a California region.\n\n Use this for area-scale questions (\"how is the Bay Area?\", \"what's\n happening in SoCal?\") instead of stitching together point queries. It\n sweeps every source over the whole region at once: CHP incidents\n (severity-sorted, worst first), lane closures in place (full closures\n called out), chain controls, and wildfires inside the region.\n\n Regions: Bay Area, Sacramento metro, Tahoe/Sierra, Central Valley,\n Southern California, San Diego, Central Coast, North State. An\n unrecognized region name returns the list.\n\n Large regions are capped to the most severe items; the counts are\n always exact and the response says when a list was truncated.\n Freshness: CHP ~1/min fetched live, everything else 5-minute cache.\n ",
"inputSchema": {
"properties": {
"region": {
"title": "Region",
"type": "string"
}
},
"required": [
"region"
],
"title": "check_regionArguments",
"type": "object"
},
"name": "check_region",
"outputSchema": null
},
{
"description": "Check current conditions along a major California highway corridor.\n\n The flagship trip-check tool: give it a start and end place and it\n returns everything active along that stretch right now - CHP incidents,\n lane closures physically in place, chain controls, and wildfires within\n ~10 miles - ordered by miles from the start, plus a summary.\n\n ALWAYS pass from_coords and to_coords (\"lat,lon\") when you know where\n the places are - for landmarks, small towns, or anything not a major\n city they are required for a good answer. Coordinates do two things:\n they let unlisted places resolve to the nearest corridor (e.g. \"Alice's\n Restaurant\" snaps to I-280 on the Peninsula), and they CLIP the route to\n the span actually being driven, so a trip to a mid-corridor destination\n doesn't report events beyond it.\n\n Corridors covered: I-80 Sacramento-Reno, US-50 to South Lake Tahoe, I-5,\n US-101, SR-17, SR-99, SR-1, I-15 to Vegas, Bay Area freeways, Tahoe-area\n routes. This is NOT a general router: if nothing matches (even with\n coordinates), the response lists the covered corridors; fall back to the\n filtered tools with center= for anything else.\n\n Freshness: CHP incidents refresh about once a minute; closures, chain\n controls, and fires are on a 5-minute cache. Current conditions only -\n this cannot forecast tomorrow's weather or closures.\n ",
"inputSchema": {
"properties": {
"from_coords": {
"anyOf": [
{
"type": "string"
},
{
"type": "null"
}
],
"default": null,
"title": "From Coords"
},
"from_place": {
"title": "From Place",
"type": "string"
},
"to_coords": {
"anyOf": [
{
"type": "string"
},
{
"type": "null"
}
],
"default": null,
"title": "To Coords"
},
"to_place": {
"title": "To Place",
"type": "string"
}
},
"required": [
"from_place",
"to_place"
],
"title": "check_routeArguments",
"type": "object"
},
"name": "check_route",
"outputSchema": null
},
{
"description": "Live Caltrans roadside camera snapshots near a point or on a route.\n\n Data: ~3,000 in-service Caltrans cameras statewide. Every returned\n image_url was verified live moments ago (offline cameras that serve a\n placeholder frame are filtered out), so images can be shown directly.\n Snapshots refresh roughly every minute; stream_url (when present) is\n an HLS video stream.\n\n Filters: center \"lat,lon\" (required unless route is given) with\n radius_km; route (e.g. \"I-80\", \"50\") narrows to that highway. Results\n sort nearest-first when a center is given. Use a camera to let the\n user SEE conditions: fog on the pass, snow on the pavement, traffic\n density at an interchange.\n ",
"inputSchema": {
"properties": {
"center": {
"anyOf": [
{
"type": "string"
},
{
"type": "null"
}
],
"default": null,
"title": "Center"
},
"limit": {
"default": 6,
"title": "Limit",
"type": "integer"
},
"radius_km": {
"default": 30,
"title": "Radius Km",
"type": "number"
},
"route": {
"anyOf": [
{
"type": "string"
},
{
"type": "null"
}
],
"default": null,
"title": "Route"
}
},
"title": "get_camerasArguments",
"type": "object"
},
"name": "get_cameras",
"outputSchema": null
},
{
"description": "Current chain-control requirements on California mountain highways.\n\n Data: Caltrans chain-control status for fixed checkpoints on mountain\n routes (I-80 Donner, US-50 Echo Summit, SR-88, SR-89, and others).\n Levels: R-1 = chains OR snow tires required; R-2 = chains required\n except 4WD/AWD with snow tires on all four; R-3 = chains on ALL vehicles\n (rare, usually precedes closure). Refresh: 5-minute cache.\n\n Filters: route (e.g. \"80\", \"US-50\", \"SR-88\"); center \"lat,lon\" with\n radius_km for all checkpoints around a place (e.g. around Truckee),\n whatever highway they are on.\n\n Off-season (roughly May-October) there are usually no controls anywhere;\n the response says so explicitly rather than returning an empty list.\n Chain requirements can change hour to hour in storms - tell the user the\n data_as_of time and to carry chains anyway when snow is possible.\n ",
"inputSchema": {
"properties": {
"center": {
"anyOf": [
{
"type": "string"
},
{
"type": "null"
}
],
"default": null,
"title": "Center"
},
"radius_km": {
"default": 40,
"title": "Radius Km",
"type": "number"
},
"route": {
"anyOf": [
{
"type": "string"
},
{
"type": "null"
}
],
"default": null,
"title": "Route"
}
},
"title": "get_chain_controlsArguments",
"type": "object"
},
"name": "get_chain_controls",
"outputSchema": null
},
{
"description": "Live CHP traffic incidents statewide, optionally filtered.\n\n Data: the California Highway Patrol statewide computer-aided dispatch\n feed - collisions, traffic hazards, disabled vehicles, closures as CHP\n logs them. Refreshes about once a minute; incidents disappear when CHP\n closes the log. Fetched live on every call.\n\n Filters (combinable):\n - highway: a route like \"I-80\", \"US 50\", \"17\", \"Hwy 99\". Matches\n incidents whose location text mentions that route.\n - center: \"lat,lon\" with radius_km - incidents within that circle. THIS\n IS THE RIGHT FILTER FOR A TOWN OR PLACE NAME: use your knowledge of\n where the place is (e.g. Coyote, CA -> \"37.22,-121.74\") with radius_km\n 15-30. A circle catches every road around the place, not just one\n highway.\n - area: substring match on the CHP dispatch-area name. These are CHP\n communication-center names (\"Hollister Gilroy\", \"East Sac\", \"Golden\n Gate\"), NOT town names - do not pass a town here. There is no county\n filter because CHP's feed carries no county field; for a county, use\n center on the county seat with a radius covering the county.\n\n Limits: locations are free-text from dispatchers; a few incidents lack\n usable coordinates and are omitted. No history - current logs only.\n ",
"inputSchema": {
"properties": {
"area": {
"anyOf": [
{
"type": "string"
},
{
"type": "null"
}
],
"default": null,
"title": "Area"
},
"center": {
"anyOf": [
{
"type": "string"
},
{
"type": "null"
}
],
"default": null,
"title": "Center"
},
"highway": {
"anyOf": [
{
"type": "string"
},
{
"type": "null"
}
],
"default": null,
"title": "Highway"
},
"radius_km": {
"default": 40,
"title": "Radius Km",
"type": "number"
}
},
"title": "get_incidentsArguments",
"type": "object"
},
"name": "get_incidents",
"outputSchema": null
},
{
"description": "Caltrans lane and road closures physically in place RIGHT NOW.\n\n Data: the Caltrans Lane Closure System (LCS). Only closures that crews\n have actually established (CHP code 1097) and not yet picked up are\n returned - scheduled-but-not-started closures are excluded, so this is\n \"what is blocking lanes now\", not a construction calendar.\n Refresh: 5-minute cache over per-district Caltrans feeds.\n\n Filters: route (e.g. \"I-80\", \"US 101\", \"1\"); district (Caltrans district\n 1-12, e.g. 3 = Sacramento/Tahoe, 4 = Bay Area, 7 = Los Angeles);\n center \"lat,lon\" with radius_km - closures whose begin or end point is\n inside the circle. For a town or place, center is the filter that\n catches work on EVERY road around it, including small state routes.\n\n Read closure_class on each record, it is what the closure means for\n through traffic:\n - \"full-roadway\": the road itself is closed in that direction. The only\n class that means \"you can't drive through\".\n - \"ramp\": a ramp or connector is closed (even when the raw record says\n \"Full\", that means the ramp is fully closed, not the highway).\n - \"one-way-traffic\": alternating single lane with flagging; passable\n with delays. Common on two-lane mountain roads.\n - \"alternating-lanes\", \"moving\", \"traffic-break\": rolling or brief work;\n minor delays.\n - \"lane\": some lanes closed; the lanes field says how many of how many.\n estimated_delay_minutes is present when crews reported one.\n Shoulder-only work is excluded entirely.\n ",
"inputSchema": {
"properties": {
"center": {
"anyOf": [
{
"type": "string"
},
{
"type": "null"
}
],
"default": null,
"title": "Center"
},
"district": {
"anyOf": [
{
"type": "integer"
},
{
"type": "null"
}
],
"default": null,
"title": "District"
},
"radius_km": {
"default": 40,
"title": "Radius Km",
"type": "number"
},
"route": {
"anyOf": [
{
"type": "string"
},
{
"type": "null"
}
],
"default": null,
"title": "Route"
}
},
"title": "get_lane_closuresArguments",
"type": "object"
},
"name": "get_lane_closures",
"outputSchema": null
},
{
"description": "Live road events near a point anywhere CommuteScout covers, not\n just California: 37 states today, growing.\n\n Data: the same multi-state feeds the live map shows, normalized -\n state DOT incidents, roadwork and closures, chain and traction\n advisories, and nationwide wildfires. Every event names its\n publishing agency in the source field. Coverage varies by state\n (some publish roadwork only; docs/state-coverage.md has the\n matrix); states added later appear here automatically.\n\n For CALIFORNIA questions prefer the dedicated tools above (richer\n detail: dispatch logs, lane counts, chain levels). Use THIS tool\n for any location outside California, near a state border, or as a\n supplement when a California tool comes back empty.\n\n center is \"lat,lon\". kinds is a comma list from: incident, closure,\n chain, fire, sign, rwis, camera, toll (toll adds live and fixed\n toll prices where agencies publish them). radius_km caps at 160.\n ",
"inputSchema": {
"properties": {
"center": {
"title": "Center",
"type": "string"
},
"kinds": {
"default": "incident,closure,chain,fire",
"title": "Kinds",
"type": "string"
},
"radius_km": {
"default": 40,
"title": "Radius Km",
"type": "number"
}
},
"required": [
"center"
],
"title": "get_nearby_eventsArguments",
"type": "object"
},
"name": "get_nearby_events",
"outputSchema": null
},
{
"description": "What Caltrans changeable message signs are displaying right now.\n\n Data: statewide CMS sign text, blank and out-of-service signs already\n filtered - every record is a message a driver is physically seeing.\n Signs carry the road's operational truth (\"CHAINS REQUIRED 10 MI\n AHEAD\", \"FULL CLOSURE HWY 96 DUE TO FIRE\", \"PREPARE TO STOP\"), often\n before the event shows up in any other feed. Refresh: ~2-minute cache.\n\n Filters: route (e.g. \"I-80\") and/or center \"lat,lon\" with radius_km.\n Quote sign text verbatim to the user - it is the most current and\n most local signal this server has.\n ",
"inputSchema": {
"properties": {
"center": {
"anyOf": [
{
"type": "string"
},
{
"type": "null"
}
],
"default": null,
"title": "Center"
},
"radius_km": {
"default": 80,
"title": "Radius Km",
"type": "number"
},
"route": {
"anyOf": [
{
"type": "string"
},
{
"type": "null"
}
],
"default": null,
"title": "Route"
}
},
"title": "get_road_signsArguments",
"type": "object"
},
"name": "get_road_signs",
"outputSchema": null
},
{
"description": "Active California wildfires, flagged when close to a major highway.\n\n Data: the interagency WFIGS current-wildfire feed (NIFC) - name, size in\n acres, percent contained, discovery date. Points are each fire's ORIGIN,\n not its perimeter: a large fire can affect roads far from this point.\n Refresh: 5-minute cache; size/containment typically update once or twice\n a day. Small, fast-moving local fires may appear in CHP incident logs\n (get_incidents, type \"FIRE-Report of Fire\") before this feed has them.\n\n Filters:\n - near_route (e.g. \"I-5\", \"101\") - only fires within ~10 miles of that\n highway's corridor line.\n - center \"lat,lon\" with radius_km - fires around a place, regardless of\n highway.\n Without either, every active CA fire is returned, each carrying a\n `near_highways` list of major corridors within ~10 miles (empty = not\n near a covered major highway; it may still affect local roads).\n\n This tool does NOT know about road closures caused by fires - cross-check\n get_incidents and get_lane_closures for the affected area.\n ",
"inputSchema": {
"properties": {
"center": {
"anyOf": [
{
"type": "string"
},
{
"type": "null"
}
],
"default": null,
"title": "Center"
},
"near_route": {
"anyOf": [
{
"type": "string"
},
{
"type": "null"
}
],
"default": null,
"title": "Near Route"
},
"radius_km": {
"default": 50,
"title": "Radius Km",
"type": "number"
}
},
"title": "get_wildfiresArguments",
"type": "object"
},
"name": "get_wildfires",
"outputSchema": null
},
{
"description": "Which major corridors have the most going on right now.\n\n Answers broad questions like \"what are the busiest routes\", \"where is\n traffic worst\", or \"which highways should I avoid today\" across all 17\n tracked corridors. by=\"activity\" ranks on live events (full closures\n weigh most, then incidents, lane closures, chain controls);\n by=\"congestion\" ranks on measured speed vs free-flow at each\n corridor's midpoint and needs the traffic feed to be configured -\n if it is not, the ranking silently falls back to activity.\n\n Each entry carries the counts and a one-line reason, so the answer\n can say WHY a corridor ranks where it does, not just list names.\n ",
"inputSchema": {
"properties": {
"by": {
"default": "activity",
"title": "By",
"type": "string"
},
"limit": {
"default": 5,
"title": "Limit",
"type": "integer"
}
},
"title": "rank_routesArguments",
"type": "object"
},
"name": "rank_routes",
"outputSchema": null
}
]
}Verify it yourself
curl -s https://api.teppi.xyz/v1/evidence/sha256:1c43b4363863db7932131a897c652d816fc8f0bb520961062969e2c8be549db3 | sha256sum