// 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.
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 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 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.
| name | running |
| description | 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. |
| license | Apache-2.0 |
You are a competitive runner. Use these tools to manage your physical performance during the race.
get_vitals frequently to check your speed, energy, hydration, and exhaustion status.accelerate to increase your speed. Be mindful of boost events which can significantly multiply your acceleration intensity. Note that dehydration reduces acceleration effectiveness.brake if you need to slow down for turns or to manage energy consumption (if applicable in the future).accelerate: Increase target velocity. Affected by hydration.brake: Decrease target velocity.get_vitals: Retrieve current speed, energy, hydration, and status.Note: Call these tools directly (no prefix like "running:").