Map Commander

Problem

Map requests often go beyond displaying a single coordinate. A user may ask for nearby restaurants, a moving friendliness score, batch geocoding for an address list, or a page that renders heat maps and routes. These cases need clear task routing, API selection, and fallback handling rather than a generic chat answer.

How it works

Map Commander routes requests by trigger phrases into five scenarios: Food Radar, Date Planner, Running Route, Moving Advisor, and Random Adventure. It also covers more engineering-oriented paths:
- POI search: for city data, nearby recommendations, restaurant or scenic spot markers.
- Batch geocoding: converting address lists into coordinates for backend processing.
- Route planning: combining origin, destination, and waypoints, with optional map rendering.
When a page display is needed, the documentation points to loading tencentmap-jsapi-gl-skill; when server-side APIs are needed, it can use tencentmap-webservice-skill. If the API returns an error, times out, lacks a valid Key, or hits quota limits, it falls back to WebSearch, querying address, POI, route, or weather keywords based on the failure type.

Boundaries

It is better treated as a map-task orchestration layer than as a system for storing accounts, managing keys, or performing complex GIS analysis. Web-search results are less precise than API results, and valid Key configuration plus API quota remain prerequisites. For production reliability, add logging, retries, and data validation.