Skip to main content
Glama

get_incidents

Read-only

Retrieve live California CHP traffic incidents filtered by highway, dispatch area, or radius around a location to check collisions, hazards, and closures.

Instructions

CALIFORNIA ONLY: live CHP traffic incidents across California, optionally filtered. For incidents in any other state use get_nearby_events (kinds='incident').

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. Fresno -> "36.74,-119.79") 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.

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": "get_incidents"
  }
}

Input Schema

NameRequiredDescriptionDefault
areaNo
centerNo
highwayNo
radius_kmNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.82.1

TDQS

A4.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety and external-data status are covered. The description still adds real value beyond them: ~1-minute refresh, incidents vanish when the CHP log closes, fetched live on every call, no history, and known completeness gaps ('a few incidents lack usable coordinates and are omitted'). It stops short of describing the shape of each returned incident record, which leaves a gap for a tool with no output schema.

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

Conciseness4/5

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

Front-loaded geographic constraint, then a labeled data paragraph, then a bulleted filter list, then a limits paragraph — a clean scan path. The all-caps emphasis lines ('THIS IS THE RIGHT FILTER FOR A TOWN OR PLACE NAME') and the follow-up justification sentence repeat the same point, which is the only real padding in an otherwise dense description.

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

Completeness4/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 still conveys the content domain (collisions, hazards, disabled vehicles, closures) and the two failure modes agents will hit (missing coordinates, no historical data). What's missing is any indication of the returned fields or result volume, so an agent doesn't know what it will get back, but nothing needed to call the tool correctly is absent.

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 carry the full burden, and it does: highway gets concrete route formats ('I-80', 'US 50', '17'), center is specified as "lat,lon" coupled with radius_km, radius_km gets suggested magnitudes (15-30 for a town, larger to cover a county), and area is explained as a CHP dispatch-area name with town names explicitly forbidden. It even narrows matching semantics (substring match on dispatch-area name; route mention in free-text location).

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?

States a specific verb and resource plus a hard scope boundary: 'CALIFORNIA ONLY: live CHP traffic incidents across California, optionally filtered.' It immediately names the sibling that handles everything else ('For incidents in any other state use get_nearby_events (kinds='incident')'), so an agent can route without opening either schema.

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?

Explicit when-to-use and when-not-to-use, plus per-filter routing guidance: use center for a town/place name, do not pass a town to area, and use center on the county seat because there is no county filter. This is exactly the decision support an agent needs for a live-data tool with four overlapping filters.

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