Skip to main content
Glama

commutescout

by io.github.nicglazkov
OverviewDiscussionsAdmin

get_incidents

Read-only

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 observed

TDQS

A4.8/5.0
Behavior5/5

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

Adds rich behavioral context beyond annotations: refresh rate, incident lifecycle (disappear when CHP closes log), live fetching, no history, and data quality issues (free-text, missing coordinates). No contradiction with annotations.

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?

Well-organized with sections (summary, data source, filters, limits). Every sentence adds value; no fluff. Information-dense yet readable.

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?

Despite no output schema, description covers data type, freshness, filtering options, limitations, and usage cautions, making the tool fully understandable and usable.

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 has 0% coverage, but description explains each parameter thoroughly: highway matches route in location text, center uses lat,lon with radius_km, area is substring on dispatch area. Includes examples and usage tips, compensating fully for missing schema descriptions.

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?

Clear verb 'get' with resource 'live CHP traffic incidents statewide, optionally filtered', and detailed data description distinguishes it from sibling tools like get_cameras or get_chain_controls.

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

Usage Guidelines4/5

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

Provides explicit guidance on when to use each filter (e.g., center for a town, area for dispatch areas) and warns not to pass a town to area. Does not explicitly compare to siblings, but context makes usage clear.

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

All commutescout toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources