Skip to main content
Glama

commutescout

by io.github.nicglazkov
OverviewDiscussionsAdmin

get_cameras

Read-only

Live Caltrans roadside camera snapshots near a point or on a route.

Data: ~3,000 in-service Caltrans cameras statewide. Every returned
image_url was verified live moments ago (offline cameras that serve a
placeholder frame are filtered out), so images can be shown directly.
Snapshots refresh roughly every minute; stream_url (when present) is
an HLS video stream.

Filters: center "lat,lon" (required unless route is given) with
radius_km; route (e.g. "I-80", "50") narrows to that highway. Results
sort nearest-first when a center is given. Use a camera to let the
user SEE conditions: fog on the pass, snow on the pavement, traffic
density at an interchange.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNo
routeNo
centerNo
radius_kmNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already indicate readOnlyHint and openWorldHint, but the description adds valuable behavioral details: images are verified live, offline cameras are filtered out, refresh rate (~1 minute), and existence of HLS stream_url. No contradictions.

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 concise, well-structured into clear sections (data, filters, usage). Every sentence adds value, and the key information is front-loaded. No wasted words.

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 read-only tool with 4 parameters and no output schema, the description covers essential behavior: data freshness, filtering, ordering, and purpose. It could mention rate limits or auth, but annotations don't hint at those. Overall complete.

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?

Schema coverage is 0%, so the description must compensate. It explains center (lat,lon), radius_km, route (with examples), and limit, plus adds ordering behavior (nearest-first when center given). This goes beyond schema structure.

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 description clearly states the tool's purpose: returning live Caltrans roadside camera snapshots near a point or on a route. It differentiates itself from sibling tools by focusing on visual conditions (fog, snow, traffic) and data quality (verified live images).

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?

The description provides explicit usage guidance: 'Use a camera to let the user SEE conditions...' and explains when to use (visual assessment) and how filtering works. It doesn't explicitly state when not to use alternatives, but the context and sibling list make it 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