Skip to main content
Glama
Sign In

CEV-OS Data API

by com.cev-os
OverviewDiscussionsAdmin

Traffic cameras (TRIPWIRE)

get_traffic_cameras
Read-onlyIdempotent

Use this when you need public traffic-camera locations and still/stream links from agency catalogs (TfL, Austin, Caltrans, TxDOT, DriveBC, Calgary, Toronto, Norway, Finland, NSW, WSDOT, King County, Catalonia, Hong Kong, DelDOT, Ontario 511). Links and metadata only; never proxied. Free. License: cleared_with_attribution. Attribution required: Traffic camera locations via CEV-OS TRIPWIRE / CEV-DataHub. Agency attribution in data.sources[].attribution. Links and metadata only; CEV-OS never proxies or stores camera images or video. Not for navigation.

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_traffic_cameras"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax cameras to return (1-2000, default 200)
sourceNoCamera catalog id (e.g. txdot_cctv, tfl_jamcam). Omit to sample across all API sources up to limit.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / source / enum
      Previous value: -[
-  "tfl_jamcam",
-  "austin_cctv",
-  "caltrans_cctv",
-  "txdot_cctv",
-  "drivebc_cctv",
-  "calgary_cctv",
-  "toronto_cctv",
-  "vegvesen_cctv",
-  "digitraffic_cctv",
-  "nsw_cctv",
-  "wsdot_cctv",
-  "kingcounty_cctv",
-  "catalonia_cctv",
-  "hongkong_cctv",
-  "deldot_cctv"
-]New value: +[
+  "tfl_jamcam",
+  "austin_cctv",
+  "caltrans_cctv",
+  "txdot_cctv",
+  "drivebc_cctv",
+  "calgary_cctv",
+  "toronto_cctv",
+  "vegvesen_cctv",
+  "digitraffic_cctv",
+  "nsw_cctv",
+  "wsdot_cctv",
+  "kingcounty_cctv",
+  "catalonia_cctv",
+  "hongkong_cctv",
+  "deldot_cctv",
+  "ontario511_cctv"
+]
  2. Added

TDQS

A4/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/openWorld, but the description adds substantial context beyond them: links are never proxied or stored, the data is free, license is cleared_with_attribution, attribution is mandatory with a specific string, and per-source attribution lives at data.sources[].attribution. That is exactly the behavioral and legal context an agent needs before surfacing results.

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

Conciseness3/5

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

The opening clause and the "Not for navigation" close are well placed and front-loaded, but the claim "Links and metadata only" appears twice in near-identical form, and the long agency roster duplicates the source enum. Trimming the repetition would make it noticeably tighter.

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?

Covers scope, licensing, attribution mechanics and a return-path hint (data.sources[].attribution), which is strong for a two-parameter read tool with no output schema. Pagination and the overall response shape are left implicit, a minor gap.

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

Parameters3/5

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

Schema description coverage is 100%, so limit bounds and the omit-to-sample-across-all behavior are already documented in the schema. The description's enumeration of agencies loosely mirrors the source enum values (TfL, Austin, Caltrans, etc.) but adds no new parameter-level meaning beyond what the schema states.

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

Purpose4/5

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

States a specific verb and resource: public traffic-camera locations plus still/stream links from a named list of agency catalogs. It does not explicitly differentiate itself from the sibling get_worldcams, so an agent must infer the distinction from the domain wording.

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?

"Use this when you need public traffic-camera locations and still/stream links" gives a clear trigger, and "Not for navigation" provides an explicit exclusion. It stops short of naming an alternative tool (e.g. get_worldcams) or stating what to use instead.

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

All CEV-OS Data API 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