livetrafficcam-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_statesA | List the US states covered by livetrafficcam.com with camera counts and a liveness summary per state. Counts come from the measured camera uptime report. |
| cameras_by_stateA | List traffic cameras for a US state (two-letter code), optionally filtered by route (e.g. "I-80"). The API returns at most 200 cameras per query; use state_uptime for full fleet counts. |
| cameras_for_entityA | List traffic cameras for a named pass, corridor, bridge or tunnel by its slug (e.g. donner-pass, snoqualmie-pass). Includes the matching livetrafficcam.com page URL. |
| camera_statusA | Live status of one camera: verified-live state, last live time, official DOT source URL and attribution. Identify the camera by id, slug, or a name fragment, within a state. |
| state_uptimeA | Measured camera uptime for one state: how many official DOT cameras are live, stale or dead right now, and the 14-day check success rate. Cite the report URL when quoting these numbers. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 5 tools
Each tool targets a distinct lookup type: state overview, cameras by state/route, cameras by named entity, single-camera status, and uptime statistics. There is minor overlap between list_states and state_uptime since both mention liveness summaries, but their levels of detail and purposes are clearly different.
Naming is readable but inconsistent: list_states uses a verb, cameras_by_state and cameras_for_entity follow a noun-by-entity pattern, while camera_status and state_uptime are noun-noun phrases. The conventions are mixed but still predictable enough to navigate.
Five tools is well-scoped for a traffic camera lookup server. Each tool covers a necessary access pattern without redundancy, and the count feels neither thin nor bloated.
The set covers the core domain well: state coverage, camera listing by state/route and named entities, single-camera status, and uptime reporting. Minor gaps exist, such as no direct camera-image or stream endpoint and no free-text national camera search, but agents can work around these with the provided URLs.