Skip to main content
Glama
Sign In

commutescout

by io.github.nicglazkov
OverviewDiscussionsAdmin

get_nearby_events

Read-only

Live road events near a point anywhere CommuteScout covers, not just California: 37 states today (get_coverage lists them).

Data: the same multi-state feeds the live map shows, normalized -
state DOT incidents, roadwork and closures, chain and traction
advisories, and nationwide wildfires. Every event names its
publishing agency in the source field. Coverage varies by state
(some publish roadwork only; docs/state-coverage.md has the
matrix); states added later appear here automatically.

For CALIFORNIA questions prefer the dedicated tools above (richer
detail: dispatch logs, lane counts, chain levels). Use THIS tool
for any location outside California, near a state border, or as a
supplement when a California tool comes back empty.

center is "lat,lon"; or pass place (an address or place name)
instead. kinds is a comma list from: incident, closure, chain, fire,
sign, rwis, camera, toll (toll adds live and fixed toll prices where
agencies publish them), enforcement (speed and red-light cameras
from OpenStreetMap). radius_km caps at 160.

Input Schema

NameRequiredDescriptionDefault
kindsNoincident,closure,chain,fire
placeNo
centerNo
radius_kmNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • addedInput schema / properties / center / anyOf
      Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]
    • addedInput schema / properties / center / default
      Added value: +null
    • removedInput schema / properties / center / type
      Removed value: -"string"
    • addedInput schema / properties / place
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Place"
+}
    • removedInput schema / required
      Removed value: -[
-  "center"
-]
  2. Added

TDQS

A4.5/5.0
Behavior4/5

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

Annotations declare readOnlyHint and openWorldHint, and the description adds real value beyond them: multi-state normalization, that every event names its publishing agency in the source field, that coverage varies per state (some roadwork-only), and that newly added states appear automatically. It does not describe the event record shape or result ordering, keeping it short of a 5.

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?

Well front-loaded: scope and data sources first, then California-escalation guidance, then parameter guidance. It is somewhat long and references external docs (state-coverage.md), but nearly every line carries actionable information.

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?

For a 4-optional-param, read-only, open-world lookup with no output schema, the description covers scope, data provenance, per-state variability, escalation rules, and all four parameters. The main omission is a hint about what a returned event contains beyond the source field.

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

Parameters4/5

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

With 0% schema coverage the description must carry the parameter burden, and it largely does: center as 'lat,lon', place as an alternative address/name, kinds as a comma list with per-value meaning (including that toll adds live and fixed prices), and radius_km capped at 160. It omits the default values (radius 40, default kinds set), which leaves a minor gap.

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 (live road events near a point) with an explicit geographic scope (37 states, not just California). It directly distinguishes itself from the dedicated California sibling tools by naming what they offer that this one does not.

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?

Gives explicit when-to-use routing: prefer the dedicated California tools for California questions, use THIS tool outside California, near a border, or as a fallback when a California tool returns empty. It also points to get_coverage for state lists, covering both selection and exclusion conditions.

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