Skip to main content
Glama
tomtom-international

TomTom MCP Server

Official
by tomtom-international
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

TomTom EV Charging Search

tomtom-ev-search
Read-onlyIdempotent

Locate EV charging stations by position, connector type, and minimum power level, with optional radius, country, and brand filters. Results list station details but not real-time charger availability.

Instructions

Find EV charging stations with their connector types and power levels. Results carry no real-time charger availability.

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum number of results (1-100). Default: 10.
queryNoSearch query for EV charging stations. Can be a station name or brand (e.g., 'Tesla Supercharger', 'ChargePoint'). Leave empty to find all nearby stations.
cursorNoThe next page of results: the nextCursor of the previous response, with the same other parameters.
radiusNoSearch radius in meters. Without it, results are biased toward position with no distance limit. Examples: 1000 (walking), 5000 (local), 20000 (wide area).
show_uiNoRequest the interactive map widget. Only hosts that support MCP Apps render it. It adds no coordinates to the text response. Default: false
languageNoLanguage for results (IETF tag). Examples: 'en-US', 'de-DE', 'fr-FR'.
positionYesCenter position as [longitude, latitude] for EV station search (GeoJSON convention). Required for location-based results. Example: [4.89707, 52.377956] for Amsterdam.
countriesNoLimit results to countries (ISO alpha-2 codes). Example: ['US'], ['DE', 'FR'].
minPowerKWNoMinimum charging power in kW. Examples: 7 (slow AC), 22 (fast AC), 50 (DC fast), 150 (ultra-fast DC).
connectorTypesNoFilter by EV connector types: 'IEC62196Type2CableAttached' is Type 2/Mennekes, 'IEC62196Type2CCS' CCS2, 'IEC62196Type1CCS' CCS1, 'IEC62196Type1' Type 1/J1772, 'StandardHouseholdCountrySpecific' a domestic plug.
response_detailNoResponse detail level. 'compact' (default): essential fields and point coordinates, saves tokens. 'full': the raw API response with every field, lossless and much larger.compact

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.6.13

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description adds a genuinely useful caveat beyond that: results carry no real-time charger availability, which prevents an agent from over-promising live status. It does not mention pagination or the compact/full default, but that is documented in the schema.

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?

Two sentences, zero waste, with the core capability front-loaded and the limitation immediately after. Nothing is repeated from the schema or annotations.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For an 11-parameter open-world search tool the description is thin: it never mentions the required position/GeoJSON convention, radius behavior, or paging, and it gives no routing guidance among the many sibling search tools. Those gaps are partly absorbed by the very rich schema and annotations, so it is adequate but not complete.

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 every parameter, including enum values and examples for connectorTypes and minPowerKW, is documented in the schema itself. The description adds no parameter meaning beyond that, so the baseline 3 applies.

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?

The description states a specific verb and resource (find EV charging stations) plus what the results contain (connector types, power levels). It implicitly separates itself from generic search siblings by naming EV charging as the domain, though it never names an alternative tool explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied: an agent can infer it should call this when the task involves EV chargers rather than general POIs. There is no explicit when-to-use, when-not-to-use, or pointer to siblings like tomtom-poi-search or tomtom-nearby for non-EV searches.

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