ZV-2026-0601 · 2026-09-01 · mcp.mapmap.ai

mcp.mapmap.ai: Type of query on geocode changed string → string|null.

breaking

What changed

Type of query on geocode changed string → string|null.

What to do

If your agents call mcp.mapmap.ai, pin the new snapshot, patch the affected call sites, and let a green contract check confirm the fix. If you don't use the changed tools, nothing is required, but the rest of the ecosystem just learned about it at the same moment you did.

The redline

−  string
+  string|null   geocode
−  Turn a free-text place query (address, POI, town) into coordinates. Returns up to `limit` …
+  Turn a place (address, POI, town) into coordinates. Ask two ways, and they combine: `query…   geocode
+  city  Optional field city was added to geocode; may shift model behaviour.
+  country  Optional field country was added to geocode; may shift model behaviour.
+  housenumber  Optional field housenumber was added to geocode; may shift model behaviour.
+  postcode  Optional field postcode was added to geocode; may shift model behaviour.
+  street  Optional field street was added to geocode; may shift model behaviour.
+  cheapest_charging_along_route  Tool cheapest_charging_along_route was added.
+  get_usage  Tool get_usage was added.
+  list_place_categories  Tool list_place_categories was added.
+  match_trace  Tool match_trace was added.
+  plan_ev_route  Tool plan_ev_route was added.
−  query  Field query on geocode is no longer required.
Full mcp.mapmap.ai changelog →JSON feedWatch this for my agents