Skip to main content
Glama
tomtom-international

TomTom MCP Server

Official
by tomtom-international
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

TomTom Traffic

tomtom-traffic
Read-onlyIdempotent

Retrieve traffic incidents in an area, including accidents, closures, and congestion. Get severity, description, delay, and affected roads to assess road conditions.

Instructions

Find and display traffic incidents in an area. The primary tool for questions about traffic, accidents, road closures, congestion, or dangerous road conditions. Returns detailed incident data including severity, description, delay, and affected roads. Provides complete traffic incident data on its own; plotting incidents as markers with tomtom-dynamic-map is not needed.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
bboxNoBounding box for traffic area: 'minLon,minLat,maxLon,maxLat'. Example: '-74.02,40.70,-73.96,40.80' for lower Manhattan. Use smaller areas for better results.
languageNoLanguage for incident descriptions: 'en-GB', 'de-DE', 'fr-FR', 'es-ES'. Default: 'en-GB'.
maxResultsNoMaximum incidents to return (1-1000). Default: 100. Use 10-20 for readability in high-traffic areas. When more incidents match, the most severe are returned and the response includes an incidentSummary with full totals.
categoryFilterNoFilter by incident categories (comma-separated): '0' (Accident), '1' (Fog), '2' (Dangerous Conditions), '3' (Rain), '4' (Ice), '5' (Lane Restrictions), '6' (Lane Closure), '7' (Road Closure), '8' (Road Works), '9' (Wind), '10' (Flooding), '11' (Detour), '14' (Cluster).
response_detailNoResponse detail level. 'compact' (default): trimmed response with essential fields only, saves tokens. 'full': complete API response with all fields including coordinates, classifications, etc.compact
timeValidityFilterNoTime validity filter: 'present' (current), 'future' (upcoming). Default: 'present'.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed8 schema fields changedv1.6.8
    • removedInput schema / additionalProperties
      Removed value: -false
    • removedInput schema / properties / incidentTypes
      Removed value: -{
-  "description": "Filter by incident types (comma-separated): '0' (Accident), '1' (Fog), '4' (Ice), '5' (Lane Restrictions), '7' (Closure), '8' (Roadworks).",
-  "type": "string"
-}
    • changedInput schema / properties / language / description
      Previous value: -"Language for incident descriptions: 'en-US', 'de-DE', 'fr-FR', 'es-ES'. Default: 'en-US'."New value: +"Language for incident descriptions: 'en-GB', 'de-DE', 'fr-FR', 'es-ES'. Default: 'en-GB'."
    • changedInput schema / properties / maxResults / description
      Previous value: -"Maximum incidents to return (1-1000). Use 10-20 for readability in high-traffic areas."New value: +"Maximum incidents to return (1-1000). Default: 100. Use 10-20 for readability in high-traffic areas. When more incidents match, the most severe are returned and the response includes an incidentSummary with full totals."
    • addedInput schema / properties / response_detail
      Added value: +{
+  "default": "compact",
+  "description": "Response detail level. 'compact' (default): trimmed response with essential fields only, saves tokens. 'full': complete API response with all fields including coordinates, classifications, etc.",
+  "enum": [
+    "compact",
+    "full"
+  ],
+  "type": "string"
+}
    • removedInput schema / properties / t
      Removed value: -{
-  "description": "Unix Timestamp in seconds for traffic model. Use current time if not provided.",
-  "type": "number"
-}
    • removedInput schema / properties / timeFilter
      Removed value: -{
-  "description": "Time validity filter: 'present' (current), 'future' (upcoming), 'all' (both). Default: 'present'.",
-  "enum": [
-    "present",
-    "future"
-  ],
-  "type": "string"
-}
    • addedInput schema / properties / timeValidityFilter
      Added value: +{
+  "description": "Time validity filter: 'present' (current), 'future' (upcoming). Default: 'present'.",
+  "enum": [
+    "present",
+    "future"
+  ],
+  "type": "string"
+}
  2. First observedv1.0.0

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, covering the safety profile. The description adds valuable behavioral context beyond that: it specifies the return content ('severity, description, delay, and affected roads') and asserts self-sufficiency ('Provides complete traffic incident data on its own'), which informs the agent about output expectations without contradicting any annotation.

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 four sentences, each earning its place: purpose, usage context, return data, and an explicit exclusion. It is front-loaded with the primary function and avoids redundancy, making it efficient and scannable for an agent.

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?

With no output schema, the description compensates by naming key return fields (severity, description, delay, affected roads). It also clarifies that the tool returns complete data on its own, eliminating the need for a mapping tool. All six parameters are fully documented in the schema, and annotations cover safety, so nothing an agent needs to call it correctly is missing.

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% with detailed per-parameter explanations (e.g., bbox example, maxResults bounds and default, categoryFilter enumeration). The description itself adds no parameter-specific meaning, but since the schema already carries the full burden, the baseline score of 3 applies.

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-resource pair: 'Find and display traffic incidents in an area.' It further differentiates itself as 'The primary tool for questions about traffic, accidents, road closures, congestion, or dangerous road conditions' and explicitly states that plotting with tomtom-dynamic-map is not needed, making its scope and identity unmistakable.

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?

The description provides explicit when-to-use guidance: it is the primary tool for all traffic-related queries, enumerating example scenarios. It also gives a clear when-not-to-use instruction by stating that tomtom-dynamic-map is not needed for plotting, effectively naming the alternative and the condition that excludes it.

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

Deploy Server

Other Tools