MapMap

cheapest_charging_along_route

Find the best EV charge points along a route, with the REAL extra travel time of stopping at each one, never a straight-line guess. Provide origin + destination (a route is computed) or an existing route's geometry_polyline6, plus optional connectors ("ccs", "type2", "chademo", "type1", "tesla", "domestic", "other"), min_kw (e.g. 50 for rapid only), available_only and max_detour_minutes (default 10). Charge points come from operator-published feeds, are costed through the routing engine with your costing (a truck profile makes detours respect dimensional/ADR restrictions) and ranked most powerful first, since minutes off the clock are bought with kilowatts. Each result carries max_power_kw, connector_standards, best_connector, evse_count, detour_minutes/detour_km and, where a live feed backs it, available_now. IMPORTANT: there is no national charge-point registry, every deployment covers only the operators it has onboarded, so ALWAYS show the returned coverage_note alongside the results. An empty results means "none from these operators within the detour budget", NEVER "there are no chargers here". Statuses are live only when availability_live is true; otherwise they are the values captured at the last ingest and must not be described as current. say is ALWAYS present and is the whole answer as one short spoken line, composed by the gateway with the coverage already inside the claim rather than appended to it: it scopes its superlative to the operators this deployment holds, and an empty result's line says the emptiness is about those operators. Prefer reading it verbatim to writing your own summary. Requires the MapMap gateway; answers a clear error when the deployment has no charge-point dataset. Display the returned charging_attribution with the results.

Input Schema

Name	Required	Description	Default
`truck`	No	Truck profile (dimensions + ADR declaration). Requires costing "truck"; the detours then respect dimensional/ADR restrictions.
`min_kw`	No	Keep only charge points whose best connector is rated at least this many kW (e.g. 50 for rapid charging only).
`origin`	No	Route origin (with `destination`, when no geometry is given).
`costing`	No	Costing model for the route and detour matrix: "auto" (default), "truck", "bicycle", "pedestrian" or "motor_scooter".	auto
`connectors`	No	Keep only charge points offering at least one of these connector standards: "type2", "type1", "ccs", "chademo", "tesla", "domestic" or "other". Omitted ⇒ every standard.
`destination`	No	Route destination.
`max_results`	No	Maximum results (default 5, at most 25).
`available_only`	No	Keep only charge points with a bay reported free right now. Needs the deployment to have a live availability feed; without one the call is refused rather than silently returning nothing.
`geometry_polyline6`	No	An existing route geometry as an encoded polyline6 (the `route` tool's `geometry_polyline6`). Provide either this or `origin` + `destination`, not both.
`max_detour_minutes`	No	Largest acceptable detour in minutes (default 10, at most 120).

Output Schema

Name	Required	Description
`say`	Yes	Always present. The whole answer as one short spoken line, composed by the gateway. Coverage is inside the claim rather than appended to it: the line scopes its superlative to the operators this deployment holds, and an empty result's line says the emptiness is about those operators, never about the road. Safe to read to a driver verbatim.
`note`	No	Why `results` is empty, when it is, the cause, not a bare list.
`costing`	Yes	The costing the detours were computed with.
`results`	Yes	Charge points within the detour budget, most powerful first (power, then detour).
`sources`	Yes	Every operator in the dataset, with its own coverage note and licence. Present even when `results` is empty.
`candidate_cap`	Yes	The matrix fan-out cap in force.
`coverage_note`	Yes	Always present. What this deployment's charge-point dataset does and does not cover. An empty `results` means "none from these operators within the budget", never "there are no chargers here". Show this to the user alongside the results.
`route_length_m`	Yes	Length of the route geometry in metres.
`route_distance_m`	No	Direct origin→destination distance in metres.
`route_duration_s`	No	Direct origin→destination travel time in seconds (same estimator as the detour legs), when routable.
`availability_live`	Yes	Whether statuses are live (a bring-your-own availability feed) or the values captured at the last ingest.
`availability_note`	Yes	Plain-language explanation of what the statuses mean here.
`candidates_costed`	Yes	Candidates actually costed through the engine (fan-out capped at `candidate_cap`, most powerful kept).
`max_detour_minutes`	Yes	The detour budget applied, minutes.
`charging_attribution`	No	Attribution string for the charge-point operators actually returned, display it with the results (a licence obligation).
`candidates_considered`	Yes	Charge points matching the filters that passed the corridor pre-filter.

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedOct 17, 2026

changedInput schema / $defs / TruckSpec / properties / tunnel_code / description

Previous value: -"ADR 8.6.4 tunnel restriction code of the load, e.g. \"B\", \"C5000D\",\n\"B/D\", or \"(—)\"/\"none\" for explicitly unrestricted. Leave unset if\nunknown: a hazmat load without a code is conservatively treated as\ncode B (allowed only through category-A tunnels)."New value: +"ADR 8.6.4 tunnel restriction code of the load, e.g. \"B\", \"C5000D\",\n\"B/D\", or \"(-)\"/\"none\" for explicitly unrestricted. Leave unset if\nunknown: a hazmat load without a code is conservatively treated as\ncode B (allowed only through category-A tunnels)."

changedOutput schema / $defs / ChargerHit / properties / available_now / description

Previous value: -"Whether a bay is free right now. Present only where a live\navailability feed backs the claim — absent means unknown, never\n\"occupied\"."New value: +"Whether a bay is free right now. Present only where a live\navailability feed backs the claim, absent means unknown, never\n\"occupied\"."

changedOutput schema / properties / charging_attribution / description

Previous value: -"Attribution string for the charge-point operators actually\nreturned — display it with the results (a licence obligation)."New value: +"Attribution string for the charge-point operators actually\nreturned, display it with the results (a licence obligation)."

changedOutput schema / properties / coverage_note / description

Previous value: -"**Always present.** What this deployment's charge-point dataset\ndoes and does not cover. An empty `results` means \"none from these\noperators within the budget\" — never \"there are no chargers here\".\nShow this to the user alongside the results."New value: +"**Always present.** What this deployment's charge-point dataset\ndoes and does not cover. An empty `results` means \"none from these\noperators within the budget\", never \"there are no chargers here\".\nShow this to the user alongside the results."

changedOutput schema / properties / note / description

Previous value: -"Why `results` is empty, when it is — the cause, not a bare list."New value: +"Why `results` is empty, when it is, the cause, not a bare list."

Changed5 schema fields changedSep 23, 2026

addedInput schema / $defs / LatLon / anyOf

Added value: +[
+  {
+    "properties": {
+      "lat": {
+        "description": "Latitude in decimal degrees (−90 to 90).",
+        "format": "double",
+        "type": "number"
+      },
+      "lon": {
+        "description": "Longitude in decimal degrees (−180 to 180).",
+        "format": "double",
+        "type": "number"
+      }
+    },
+    "required": [
+      "lat",
+      "lon"
+    ],
+    "type": "object"
+  },
+  {
+    "description": "GeoJSON position [lon, lat]: longitude FIRST.",
+    "items": {
+      "format": "double",
+      "type": "number"
+    },
+    "maxItems": 2,
+    "minItems": 2,
+    "type": "array"
+  }
+]

changedInput schema / $defs / LatLon / description

Previous value: -"A WGS84 coordinate pair in decimal degrees."New value: +"A WGS84 coordinate in decimal degrees: a {lat, lon} object (preferred), or a GeoJSON [lon, lat] array with LONGITUDE FIRST, the same order as every polygon field on this server."

removedInput schema / $defs / LatLon / properties

Removed value: -{
-  "lat": {
-    "description": "Latitude in decimal degrees (−90 to 90).",
-    "format": "double",
-    "type": "number"
-  },
-  "lon": {
-    "description": "Longitude in decimal degrees (−180 to 180).",
-    "format": "double",
-    "type": "number"
-  }
-}

removedInput schema / $defs / LatLon / required
```
Removed value: -[
-  "lat",
-  "lon"
-]
```
removedInput schema / $defs / LatLon / type
```
Removed value: -"object"
```

Changed2 schema fields changedSep 21, 2026

addedOutput schema / properties / say

Added value: +{
+  "description": "**Always present.** The whole answer as one short spoken line,\ncomposed by the gateway. Coverage is inside the claim rather than\nappended to it: the line scopes its superlative to the operators\nthis deployment holds, and an empty result's line says the\nemptiness is about those operators, never about the road. Safe to\nread to a driver verbatim.",
+  "type": "string"
+}

changedOutput schema / required

Previous value: -[
-  "costing",
-  "route_length_m",
-  "candidates_considered",
-  "candidates_costed",
-  "candidate_cap",
-  "max_detour_minutes",
-  "results",
-  "coverage_note",
-  "sources",
-  "availability_live",
-  "availability_note"
-]New value: +[
+  "costing",
+  "route_length_m",
+  "candidates_considered",
+  "candidates_costed",
+  "candidate_cap",
+  "max_detour_minutes",
+  "results",
+  "coverage_note",
+  "sources",
+  "availability_live",
+  "availability_note",
+  "say"
+]

AddedSep 1, 2026

TDQS

A4.3/5.0

Behavior5/5

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

With no annotations, the description carries the full burden and does so unusually well: it discloses coverage limitations (no national registry, per-deployment operator scope, always show coverage_note), the meaning of an empty results set, availability staleness semantics (live only when availability_live is true), the refusal behaviour of available_only, gateway/dataset prerequisites, and how ranking and costing work. These are exactly the operational traits an agent cannot derive from 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.

Conciseness4/5

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

The core purpose and input modes are front-loaded in the first sentence, and the density is high with little filler apart from the aphorism about kilowatts. It is on the long side for a tool description and mixes result-field enumeration with invocation guidance, but almost every sentence conveys actionable information.

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?

Given 10 parameters, no required fields, a rich schema, an output schema, and no annotations, the description covers everything an agent needs: input-mode selection, filtering semantics, coverage and staleness caveats, error conditions, the `say` field contract, and attribution requirements. Return fields are listed even though an output schema exists, which is mildly redundant but not a gap.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is already 100%, so the schema does the heavy lifting and a 3 would be the baseline. The description adds real meaning on top: it enumerates the connector tokens inline, explains min_kw's intent (e.g. 50 for rapid only), gives max_detour_minutes' default and cap context, and clarifies that a truck profile makes detours respect dimensional/ADR restrictions and requires costing "truck".

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 precise verb and resource — find EV charge points along a route — and adds the distinguishing scope that detours are costed through the routing engine rather than estimated as straight lines, which is genuinely differentiating. However, it never names or contrasts against the obvious siblings that could be confused with it, notably plan_ev_route and cheapest_fuel_along_route, so an agent must infer the boundary itself.

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 clearly states the input modes (origin+destination, or an existing route's geometry_polyline6, explicitly not both) and gives concrete filter conditions such as available_only requiring a live feed and being refused otherwise. It also tells the agent to prefer the returned `say` verbatim and to display charging_attribution. What is missing is any explicit when-not or alternative-tool routing against siblings like plan_ev_route or search_along_route.

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

All MapMap tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?