Skip to main content
Glama
nicglazkov

CommuteScout

by nicglazkov
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

get_incidents

Read-only

Retrieve live California Highway Patrol traffic incidents, filterable by highway, area, or location radius, to stay updated on collisions, hazards, and closures.

Instructions

Live CHP traffic incidents statewide, optionally filtered.

Data: the California Highway Patrol statewide computer-aided dispatch feed - collisions, traffic hazards, disabled vehicles, closures as CHP logs them. Refreshes about once a minute; incidents disappear when CHP closes the log. Fetched live on every call.

Filters (combinable):

  • highway: a route like "I-80", "US 50", "17", "Hwy 99". Matches incidents whose location text mentions that route.

  • center: "lat,lon" with radius_km - incidents within that circle. THIS IS THE RIGHT FILTER FOR A TOWN OR PLACE NAME: use your knowledge of where the place is (e.g. Coyote, CA -> "37.22,-121.74") with radius_km 15-30. A circle catches every road around the place, not just one highway.

  • area: substring match on the CHP dispatch-area name. These are CHP communication-center names ("Hollister Gilroy", "East Sac", "Golden Gate"), NOT town names - do not pass a town here. There is no county filter because CHP's feed carries no county field; for a county, use center on the county seat with a radius covering the county.

Limits: locations are free-text from dispatchers; a few incidents lack usable coordinates and are omitted. No history - current logs only.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
areaNo
centerNo
highwayNo
radius_kmNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.82.1

TDQS

A5/5.0
Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Beyond the readOnlyHint and openWorldHint annotations, the description discloses live-fetch behavior, approximate refresh rate, incident disappearance when CHP closes logs, missing coordinates in some incidents, and no historical data. This gives agents an accurate model of volatility and data completeness.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is organized into labeled sections, front-loaded with the core purpose, and every paragraph adds operational detail. It is long but dense with high-value guidance and contains no filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description compensates by describing the feed content and limitations. For a 4-parameter, filterable live-data tool, it covers data source, filter behavior, freshness, missing-data caveats, and non-availability of history.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, so the description must fully explain parameters, and it does. highway, center, radius_km, and area each receive concrete semantics, formatting examples, and usage caveats. It even provides a geographic example and radius recommendation.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The opening sentence states a specific verb and resource: 'Live CHP traffic incidents statewide, optionally filtered.' It clearly identifies the data source and scope, which differentiates it from sibling tools like get_cameras or get_road_signs.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description gives explicit when-to-use guidance, especially for filters: center is 'THE RIGHT FILTER FOR A TOWN OR PLACE NAME,' area is a CHP dispatch area 'NOT town names,' and county queries should use center. It also explains combinability and omits misinformation about a nonexistent county filter.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools