Skip to main content
Glama

traffic

Read-only

Retrieve live traffic conditions, congestion, and speed for a location. Use when traffic is needed independently of routing — for corridor monitoring, area congestion, or incident checks. COVERAGE: live data for ~30 major US metros; returns degraded or empty values outside these areas. For rural coordinates, qualify the response (e.g. 'no live traffic coverage here — showing free-flow speeds').

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "lat": "<lat>",
      "lon": "<lon>"
    },
    "name": "traffic"
  }
}

Input Schema

NameRequiredDescriptionDefault
latYesLatitude
lonYesLongitude
unitsNoSpeed units — auto-detected from location (mph in US/UK, km/h elsewhere). Override if needed. Accepts 'km'/'mi' as aliases.

Output Schema

NameRequiredDescriptionDefault
itemsNo
geojsonNo
metricsNo
summaryNoMap of scalar facts the LLM should surface verbatim
display_hintNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed8 schema fields changed
    • changedOutput schema / additionalProperties
      Previous value: -trueNew value: +{}
    • changedOutput schema / properties / display_hint / additionalProperties
      Previous value: -trueNew value: +{}
    • changedOutput schema / properties / geojson / additionalProperties
      Previous value: -trueNew value: +{}
    • changedOutput schema / properties / geojson / properties / features / items / additionalProperties
      Previous value: -trueNew value: +{}
    • changedOutput schema / properties / geojson / properties / features / items / properties / geometry / anyOf
      Previous value: -[
      -  {
      -    "additionalProperties": true,
      -    "properties": {
      -      "coordinates": {},
      -      "geometries": {
      -        "items": {},
      -        "type": "array"
      -      },
      -      "type": {
      -        "anyOf": [
      -          {
      -            "enum": [
      -              "Point",
      -              "LineString",
      -              "Polygon",
      -              "MultiPoint",
      -              "MultiLineString",
      -              "MultiPolygon",
      -              "GeometryCollection"
      -            ],
      -            "type": "string"
      -          },
      -          {
      -            "type": "string"
      -          }
      -        ]
      -      }
      -    },
      -    "required": [
      -      "type"
      -    ],
      -    "type": "object"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]New value: +[
      +  {
      +    "additionalProperties": {},
      +    "properties": {
      +      "coordinates": {},
      +      "geometries": {
      +        "items": {},
      +        "type": "array"
      +      },
      +      "type": {
      +        "anyOf": [
      +          {
      +            "enum": [
      +              "Point",
      +              "LineString",
      +              "Polygon",
      +              "MultiPoint",
      +              "MultiLineString",
      +              "MultiPolygon",
      +              "GeometryCollection"
      +            ],
      +            "type": "string"
      +          },
      +          {
      +            "type": "string"
      +          }
      +        ]
      +      }
      +    },
      +    "required": [
      +      "type"
      +    ],
      +    "type": "object"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • addedOutput schema / properties / geojson / properties / features / items / properties / properties / propertyNames
      Added value: +{
      +  "type": "string"
      +}
    • addedOutput schema / properties / items / items / propertyNames
      Added value: +{
      +  "type": "string"
      +}
    • addedOutput schema / properties / summary / propertyNames
      Added value: +{
      +  "type": "string"
      +}
  2. Changed6 schema fields changed
    • addedInput schema / properties / lat / maximum
      Added value: +90
    • addedInput schema / properties / lat / minimum
      Added value: +-90
    • addedInput schema / properties / lon / maximum
      Added value: +180
    • addedInput schema / properties / lon / minimum
      Added value: +-180
    • changedOutput schema / additionalProperties
      Previous value: -falseNew value: +true
    • addedOutput schema / properties / metrics
      Added value: +{}
  3. Changed1 schema field changed
    • changedInput schema / properties / units / description
      Previous value: -"Speed units — auto-detected from location (mph in US/UK, km/h elsewhere). Override if needed."New value: +"Speed units — auto-detected from location (mph in US/UK, km/h elsewhere). Override if needed. Accepts 'km'/'mi' as aliases."
  4. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "$schema": "http://json-schema.org/draft-07/schema#",
      +  "additionalProperties": false,
      +  "properties": {
      +    "display_hint": {
      +      "additionalProperties": true,
      +      "properties": {
      +        "layout": {
      +          "anyOf": [
      +            {
      +              "enum": [
      +                "summary",
      +                "table",
      +                "summary+table",
      +                "map",
      +                "chart+table"
      +              ],
      +              "type": "string"
      +            },
      +            {
      +              "type": "string"
      +            }
      +          ]
      +        },
      +        "map_layers": {
      +          "items": {
      +            "type": "string"
      +          },
      +          "type": "array"
      +        },
      +        "preferred_charts": {
      +          "items": {
      +            "type": "string"
      +          },
      +          "type": "array"
      +        },
      +        "sections": {
      +          "items": {
      +            "type": "string"
      +          },
      +          "type": "array"
      +        }
      +      },
      +      "required": [
      +        "layout"
      +      ],
      +      "type": "object"
      +    },
      +    "geojson": {
      +      "additionalProperties": true,
      +      "properties": {
      +        "features": {
      +          "items": {
      +            "additionalProperties": true,
      +            "properties": {
      +              "geometry": {
      +                "anyOf": [
      +                  {
      +                    "additionalProperties": true,
      +                    "properties": {
      +                      "coordinates": {},
      +                      "geometries": {
      +                        "items": {},
      +                        "type": "array"
      +                      },
      +                      "type": {
      +                        "anyOf": [
      +                          {
      +                            "enum": [
      +                              "Point",
      +                              "LineString",
      +                              "Polygon",
      +                              "MultiPoint",
      +                              "MultiLineString",
      +                              "MultiPolygon",
      +                              "GeometryCollection"
      +                            ],
      +                            "type": "string"
      +                          },
      +                          {
      +                            "type": "string"
      +                          }
      +                        ]
      +                      }
      +                    },
      +                    "required": [
      +                      "type"
      +                    ],
      +                    "type": "object"
      +                  },
      +                  {
      +                    "type": "null"
      +                  }
      +                ]
      +              },
      +              "id": {
      +                "type": [
      +                  "string",
      +                  "number"
      +                ]
      +              },
      +              "properties": {
      +                "additionalProperties": {},
      +                "type": "object"
      +              },
      +              "type": {
      +                "const": "Feature",
      +                "type": "string"
      +              }
      +            },
      +            "required": [
      +              "type",
      +              "geometry"
      +            ],
      +            "type": "object"
      +          },
      +          "type": "array"
      +        },
      +        "type": {
      +          "const": "FeatureCollection",
      +          "type": "string"
      +        }
      +      },
      +      "required": [
      +        "type",
      +        "features"
      +      ],
      +      "type": "object"
      +    },
      +    "items": {
      +      "items": {
      +        "additionalProperties": {},
      +        "type": "object"
      +      },
      +      "type": "array"
      +    },
      +    "summary": {
      +      "additionalProperties": {},
      +      "description": "Map of scalar facts the LLM should surface verbatim",
      +      "type": "object"
      +    }
      +  },
      +  "type": "object"
      +}
  5. Changed1 schema field changed
    • addedInput schema / additionalProperties
      Added value: +false
  6. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Beyond the readOnly and openWorld annotations, the description discloses the critical behavioral caveat: live data is limited to roughly 30 major US metros and degrades or returns empty values outside them. It even advises how to qualify rural-coordinate responses, which is exactly the kind of operational context annotations cannot provide.

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 definition is front-loaded with purpose and usage, followed by the essential coverage caveat. Every sentence adds operational value, and the rural qualification guidance is compact rather than redundant.

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?

For a live-data retrieval tool with full schema descriptions, annotations, and an output schema, this is complete. Coverage limits, degraded behavior, and response-qualification guidance are all present where they matter most.

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%, and the schema already documents lat, lon, unit options, and auto-detection. The description adds no parameter-specific syntax or constraints beyond the schema, so the baseline of 3 is appropriate.

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 opens with a specific verb and resource: retrieve live traffic conditions, congestion, and speed for a location. It also distinguishes this from routing-oriented siblings by saying traffic is needed independently of routing, so an agent can identify the tool without opening the schema.

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?

It gives clear usage contexts—corridor monitoring, area congestion, and incident checks—and explicitly contrasts this with routing use. It stops short of naming a specific routing sibling such as directions, but the intended boundary is clear.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources