Skip to main content
Glama
tomtom-international

TomTom MCP Server

Official
by tomtom-international
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

TomTom Data Visualization

tomtom-data-viz
Read-onlyIdempotent

Visualize custom GeoJSON datasets on a TomTom basemap with markers, heatmaps, clusters, and choropleth layers. Overlay multiple layers in one call and enrich point clicks with address data.

Instructions

Visualize custom GeoJSON data on a TomTom basemap. The map is drawn by the MCP app, so the visual requires a client that supports MCP apps; the caller gets back only a summary. Intended for large datasets, heatmaps, cluster maps, choropleth maps, or GeoJSON data (from a URL or inline) rendered on a map. Supports markers, heatmaps, clusters, lines, polygon fills, and choropleth maps. Provide data via HTTPS URL or inline GeoJSON. Multiple layers can be overlaid in a single call. Point features are automatically enriched with TomTom address data when clicked (reverse geocode). Placing a few specific markers, routes, or polygons is handled by tomtom-dynamic-map; route calculations (directions, travel time) are handled by tomtom-routing.

Input Schema

NameRequiredDescriptionDefault
titleNoDisplay title shown as an overlay on the map. Example: 'Store Locations'.
layersYesArray of layer configurations (max 10). Each layer defines how to visualize the data. Multiple layers can overlay different visualization types on the same data. Example: [{ type: 'heatmap' }, { type: 'markers', label_property: 'name' }].
geojsonNoInline GeoJSON string. Must be a valid FeatureCollection or Feature object. Max 10MB. Mutually exclusive with 'data_url'. For larger datasets, host the file and use 'data_url' instead.
show_uiNoRender the data on the interactive MCP app map. The visualization is the tool's only output; set to false only to validate the data without a map. Default: true.
data_urlNoHTTPS URL to fetch GeoJSON data from (server-side). Supports FeatureCollection or single Feature. Max 50MB, 30s timeout. Mutually exclusive with 'geojson'. Preferred for large datasets. Example: 'https://example.com/data.geojson'.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.6.13

TDQS

A4.6/5.0
Behavior5/5

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

Annotations cover the safety profile (readOnly, idempotent, non-destructive, openWorld), and the description adds genuinely non-obvious behavior: rendering happens in the MCP app so the caller receives only a summary, a client-side capability requirement, automatic reverse-geocode enrichment of clicked points, and implicit size/timeout constraints. None of this contradicts the annotations.

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

Conciseness4/5

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

Front-loaded with purpose and alternatives, and each sentence carries information. Slight redundancy: the enumeration of markers/heatmaps/clusters/lines/polygons largely restates the layer type enum already documented in the schema.

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 read-only rendering tool with no output schema, the description covers the essential non-schema facts an agent needs: client capability requirement, summary-only return, data source options and limits, and layer composability. Nothing critical 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%, so the baseline is 3. The description reinforces the URL-vs-inline choice and multi-layer overlay semantics, but adds no syntax or behavioral detail beyond what the per-field descriptions already state.

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?

States a specific verb and resource ('Visualize custom GeoJSON data on a TomTom basemap') plus the supported visualization repertoire. It explicitly contrasts itself with tomtom-dynamic-map and tomtom-routing, so an agent can distinguish it from siblings without opening a schema.

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?

Gives positive guidance (large datasets, heatmaps, clusters, choropleths, URL or inline GeoJSON, multi-layer overlays) and explicit exclusions with named alternatives: few markers/routes/polygons → tomtom-dynamic-map, directions/travel time → tomtom-routing. Prerequisites (client must support MCP apps) are also disclosed.

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