// Use when the marathon plan needs a 26.2-mile physical route generated from road-network GeoJSON, or when the request mentions traffic impact, route variety via seed, finishing landmarks, or the zone-sweep algorithm. Triggered by route-planning or traffic-analysis language.
Use when the marathon plan needs non-spatial event parameters defined: theme, hydration-point logistics, crowd zones, start times, or expected participant counts. Triggered when the request describes the feel or operational logistics of the race rather than its physical route.
Use when the planning committee asks about marathon finances or requests a budget change. Triggered by mentions of budget, cost, spending, sponsorship, or any phrasing that implies modifying a financial allocation. Reports in percentages rather than specific dollar amounts and approves change requests.
Use when planning a marathon route that must reference real-world geography: looking up landmarks, businesses, or parks in a city, computing distances between points, or checking historical and forecasted weather for the race date and location. Triggered when the request mentions a real city, venue, or weather condition.
Use when the planning committee asks to change, increase, decrease, or modify a budget allocation in a security-restricted context. Triggered by any budget-modification phrasing. Refuses the change and directs the requester to an authorized administrator.
Use when a runner agent receives a distance update and must deplete water proportionally, or when the runner enters a hydration station and must decide whether to stop and rehydrate. Triggered by distance events and station events.
Use when a runner agent needs to manage athletic performance during a race tick: accelerating, braking, or reading current vitals (speed, energy, hydration, exhaustion). Triggered every tick the runner is active.
| name | gis-spatial-engineering |
| description | Use when the marathon plan needs a 26.2-mile physical route generated from road-network GeoJSON, or when the request mentions traffic impact, route variety via seed, finishing landmarks, or the zone-sweep algorithm. Triggered by route-planning or traffic-analysis language. |
| license | Apache-2.0 |
| metadata | {"adk_additional_tools":["plan_marathon_route","report_marathon_route","assess_traffic_impact"]} |
You use this skill to generate the physical path of the marathon.
You have access to a road network GeoJSON located at assets/network.json.
Key features available in this network include:
properties.name (e.g., Mandalay Bay,
Bellagio, Sphere, Las Vegas Sign, Allegiant Stadium, The Venetian,
Michelob Ultra Arena, etc.).
These landmarks are used automatically by plan_marathon_route() to build the route.properties.name (e.g.,
Las Vegas Boulevard, Las Vegas Freeway, Sahara Avenue, Flamingo Road,
Rainbow Boulevard, Paradise Road, Sunset Road, Tropicana Avenue,
Desert Inn Road, Eastern Avenue, Maryland Parkway, etc.).The default algorithm is zone-sweep: the route starts at the Las Vegas Sign, goes northbound on the Strip past MGM Grand, sweeps through city zones (neighborhoods) using non-crossing geometry, and finishes near a prominent landmark (e.g., Michelob Ultra Arena). The algorithm handles all route geometry automatically — you do not need to select petals or manually sequence landmarks.
plan_marathon_route() with no arguments produces a valid
26.2-mile zone-sweep route. Use finish_landmark and seed for variety.plan_marathon_route(finish_landmark: Optional[str] = None, seed: Optional[int] = None, geojson_data: Optional[str] = None):
Generate the exact 26.2-mile path.
finish_landmark: Name of a landmark to finish near (e.g., "Michelob Ultra Arena").seed: Integer seed for route variety. Different seeds produce different routes.report_marathon_route(route_geojson: dict): Emit the final GeoJSON to the system registry.plan_marathon_route() with default arguments.seed to generate alternative routes when the user wants variety.finish_landmark when the user specifies a preferred finishing area.