MapMap

plan_day

Turn an itinerary into one navigable multi-stop route. Provide a start and stops (each a location {lat, lon} or a free-text name to geocode, plus optional dwell_minutes time at the stop), optional depart_at (RFC 3339) for absolute ETAs, optimise: true to reorder stops for the shortest day (VROOM solver), and return_to_start. Costing "auto", "truck" (with a truck profile the whole day respects dimensional/ADR restrictions), "bicycle", "pedestrian" or "motor_scooter". Returns the stops in visit order with per-leg duration/distance and arrival/departure times, totals, and the full route geometry (polyline6). Geocoded names carry a resolution — when ambiguous is true, check alternatives and re-run with an explicit location rather than trusting the guess.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`start`	Yes	Where the day starts (name or location; `dwell_minutes` ignored).
`stops`	Yes	The stops to visit (1–20). Visited in the given order unless `optimise` is true.
`truck`	No	Truck profile (dimensions + ADR declaration). Requires costing "truck".
`costing`	No	Costing model: "auto" (default), "truck", "bicycle", "pedestrian" or "motor_scooter".	auto
`optimise`	No	Reorder the stops for the shortest day (VROOM solver; requires the optimisation sidecar). Default false: visit in the given order.
`depart_at`	No	Departure time as RFC 3339 (e.g. "2026-07-18T09:00:00Z"); when given, every ETA is also returned as an absolute timestamp.
`return_to_start`	No	End the day back at the start (default false).

Output Schema

TableJSON Schema

Name	Required	Description
`start`	Yes	The day's starting point.
`stops`	Yes	The stops in visit order, each with leg, ETAs and any geocoding resolution to double-check.
`costing`	Yes	The costing the plan was routed with.
`summary`	Yes	One-line human-readable summary of the day.
`depart_at`	No	The departure time echoed back, when one was given.
`finish_at`	No	Absolute end of the day (RFC 3339), when `depart_at` was given.
`optimised`	Yes	Whether the stop order was optimised (VROOM) or kept as given.
`return_leg`	No	The leg back to the start, when `return_to_start` was set.
`total_dwell_s`	Yes	Total time at stops, seconds.
`finish_offset_s`	Yes	End of the day (last arrival + dwell), seconds after departure.
`total_distance_m`	Yes	Total travel distance, metres.
`geometry_polyline6`	Yes	Full multi-stop route geometry (polyline6) — hand it to the map SDK or the `route` tool consumers directly.
`total_travel_duration_s`	Yes	Total driving/travel time, seconds.

Schema Changelog

Changes observed during successful MCP inspections.

Changed10 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"
```

addedOutput 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"
+  }
+]

changedOutput 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."

removedOutput 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"
-  }
-}

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

Changed3 schema fields changedSep 1, 2026

addedOutput schema / $defs / GeocodeHit / properties / match

Added value: +{
+  "anyOf": [
+    {
+      "$ref": "#/$defs/GeocodeMatch"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "description": "How far this hit can be trusted to be the place that was asked\nfor — see [`GeocodeMatch`]. Present whenever the MapMap gateway\nanswered; absent on a deployment falling back to the direct Photon\ngeocoder, and absent on the gateway's own fast paths (a pasted\ncoordinate pair, a bare UK outward code, a category browse), which\nanswer without a ranking to report on."
+}

addedOutput schema / $defs / GeocodeMatch

Added value: +{
+  "description": "How well one geocoding result answers what was actually asked.\n\nGeocoding's real failure mode is not \"no answer\" but a confident answer\nto a different question: a plausible row on the wrong street, with\nnothing in the response to say so. This object is that missing say-so,\nand an agent should read it before acting on an address.\n\nHow to read it:\n\n* Any component `unmatched` or `inferred` on the TOP hit means the\n  answer does not carry the address that was asked for — an `unmatched`\n  postcode means the result has no postcode at all, `inferred` means it\n  has a different one. Neither is a match. Say so rather than presenting\n  the hit as the address, and reach for `verify_places` when the address\n  came from a model or a user and needs checking rather than using.\n* A small `score_gap` means the ranking barely chose between this hit\n  and the runner-up, which is exactly when to show the alternatives\n  instead of picking one for the user.",
+  "properties": {
+    "components": {
+      "$ref": "#/$defs/GeocodeMatchComponents",
+      "description": "Per-component verdict on this hit: one entry for each structured\ncomponent supplied, and empty when the query was free text only."
+    },
+    "score_gap": {
+      "description": "The top result's score minus the runner-up's, rounded to 3 decimal\nplaces. `0` for a single result, and `0` from the `photon` source,\nwhich publishes no per-result score — so a `0` is \"no signal\", not\n\"a tie\".",
+      "format": "double",
+      "type": "number"
+    },
+    "source": {
+      "description": "Which backend answered: \"mapmap-index\" (the first-party index) or\n\"photon\".",
+      "type": "string"
+    }
+  },
+  "required": [
+    "components",
+    "score_gap",
+    "source"
+  ],
+  "type": "object"
+}

addedOutput schema / $defs / GeocodeMatchComponents

Added value: +{
+  "description": "Per-component verdicts inside a [`GeocodeMatch`]. Each is one of\n\"matched\", \"inferred\" or \"unmatched\"; a component that was not supplied\nis absent entirely.\n\n* \"matched\" — the result's own field carries the value asked for (case-\n  and accent-insensitive, and by containment, so `city: \"London\"`\n  matches \"City of London\").\n* \"inferred\" — the result carries a value for that component, but not\n  the one asked for. It reached the page through ranking, as when a\n  street is found by its transliterated name and displayed under its\n  canonical one.\n* \"unmatched\" — the result carries no value for that component at all.",
+  "properties": {
+    "city": {
+      "description": "Verdict on the supplied `city`.",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "country": {
+      "description": "Verdict on the supplied `country`.",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "housenumber": {
+      "description": "Verdict on the supplied `housenumber`.",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "postcode": {
+      "description": "Verdict on the supplied `postcode`.",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "street": {
+      "description": "Verdict on the supplied `street`.",
+      "type": [
+        "string",
+        "null"
+      ]
+    }
+  },
+  "type": "object"
+}

First observedSep 1, 2026

TDQS

A4.3/5.0

Behavior4/5

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

With no annotations, the description carries the full burden. It discloses key behaviors: geocoding fallback, ambiguous resolution handling, VROOM optimisation, truck ADR restrictions, absolute ETAs with depart_at, and return geometry as polyline6. It also warns about ambiguous geocoding and tells the agent to re-run with explicit coordinates. This is strong behavioral disclosure beyond 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 description is dense but well-organized: it front-loads the core purpose, then walks through parameters in a logical order, and ends with the geocoding caveat. Every sentence adds information. It's slightly long but justified given the tool's complexity and the absence of annotations.

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

Completeness4/5

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

The tool has 7 parameters, an output schema, and no annotations. The description covers the main behaviors, return values, and edge cases (ambiguous geocoding). It doesn't mention error conditions (e.g., what happens if optimise is requested without the sidecar, or if truck is supplied without costing 'truck'), but the schema already notes the sidecar requirement. Overall, it's complete enough for an agent to call correctly.

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 coverage is 100%, so the baseline is 3. The description adds value by explaining how parameters interact: start + stops, dwell_minutes shifting ETAs, optimise reordering via VROOM, truck profile affecting the whole day, and depart_at enabling absolute ETAs. It also clarifies the return_to_start behavior. This goes beyond the schema's individual field descriptions.

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: 'Turn an itinerary into one navigable multi-stop route.' It clearly distinguishes this from siblings like route, optimise_routes, order_stops, and plan_errands by focusing on a full day's itinerary with stops, dwell times, costing, and return-to-start. The scope is unambiguous.

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?

The description implies when to use it (planning a multi-stop day) and contrasts with alternatives by mentioning the VROOM solver and costing options. It doesn't explicitly say 'use X instead when...' but the context is clear enough for an agent to select it over route or optimise_routes. A small gap: no explicit exclusion of single-leg routing or when to prefer plan_errands.

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?