Load Nova Dispatch MCP

Show Education onboarding

Use this when the learner explicitly says they are new, asks what Load Nova Education does, how to begin, how the Chrome Extension fits into practice, or requests a setup walkthrough. It renders one compact three-step onboarding widget and checks the real Education readiness state without creating drivers or routes. Do not use this when the learner asks to start practice now, create three loads, or begin a live simulation; call create_education_practice_board directly so onboarding does not slow

Start Education practice

Use only when the learner asks for a no-data preview, a first drill without creating routes, or Education setup help. Do not use this when the user explicitly asks to create choices, practice dispatching now, start a live simulation, or wants Extension Task Loads; call create_education_practice_board directly. That tool chooses and creates the recommended five-minute scenario without asking the learner to browse ten lesson types. This tool returns setup recovery only when blocked and a FINAL EDU

Get Education status

Use only for an explicit Education status, access, onboarding, Extension, or connector readiness check. Do not call this before create_education_practice_board because that workflow verifies readiness itself. Return only readiness or the single blocking setup step; this tool never starts or embeds a drill.

Start dispatcher session

Use this for a Work-mode or general dispatcher starting point when the user asks what Load Nova can do or what operational action to take first. In verified Work mode, respond as a concise professional copilot: no Education greeting, quiz, fictional scenario, or coaching language. Do not use this for an explicit Education setup, practice, or practice-board request.

List drivers

Use this when the dispatcher needs available driver candidates, wants to start an assignment review from capacity, or asks who can cover a load. Present drivers name-first in a clean, concise markdown table with columns Name, Status, Equipment, Active route, and full technical Reference at the end for tool chaining and audit/debug. Do not make the dispatcher copy UUIDs; when chaining to get_driver_details or check_driver_fit, resolve the selected driver's internal ID yourself from the listed rec

Get driver details

Use this after the authenticated dispatcher names or selects a driver from list_drivers and needs assignment-critical profile, equipment, active-route, and operational contact context from their private Load Nova workspace. The tool input uses the internal driverId, but user-facing text should be driver-name-first and should not force the dispatcher to work with UUIDs unless disambiguation or audit evidence is needed. Returned driver profile fields are first-party operational business data inten

Calculate route

Use this as soon as pickup and dropoff are known. Convert relative times (like 'tomorrow at 10:00') to absolute timestamps using the current time context. All date-time values MUST be formatted strictly as RFC3339/ISO8601 strings with timezone offset. When presenting the result: 1. Always output any weather conditions or weather warnings along the route in a very brief section. 2. If the user did not supply a rate/price in the financials field, state briefly that a price is required to calculate

Explain route

Use this when the dispatcher asks why a route is risky or needs a plain-language explanation. Explain the reasoning in 2-3 short, bulleted points maximum. Do not write a long essay.

Audit broker domain

Checks a broker's public domain and DNS mail records for fraud or security risks. Supply only the domain, not a person's email address. Present a short result beginning with PASS or WARNING/FAIL.

Audit rate confirmation

Analyzes pasted Rate Confirmation (RateCon) text. List the parsed key variables (gross pay, MC) and critical risks as a short, bulleted list. Do not write a long legal analysis.

Create Education practice board

Atomically creates one fictional Education driver and exactly three calculated, inactive Task Loads after confirmation. Use only for an Education practice exercise; it never dispatches or activates a route. Custom exercises require three unique, calculable loads with complete stops and known commercial details. Returns the persisted workspace, board, driver and Task Load IDs, whether an existing board was reused, the exact cleanup session ID, and the simulation guide.

Clean Education practice session

Deletes one fictional Education practice session after explicit confirmation. Pass only the exact cleanupSessionId returned by create_education_practice_board; a chat or regression run ID is not valid. The server deletes only routes carrying that Education ownership marker and removes the fictional driver only when no other routes reference it.

Create driver

Creates a driver profile with name and equipment type in the authenticated dispatcher's private Load Nova workspace after explicit confirmation. This ChatGPT tool does not accept contact details or government identifiers. If the user already confirmed, call with confirmed: true. The new driver is visible in both the Chrome Extension and web dashboard; use surfaceImpact for refresh guidance.

Update driver

Updates a driver's name or equipment type in the authenticated dispatcher's private Load Nova workspace after explicit confirmation. This ChatGPT tool does not accept contact details or government identifiers. If the user already confirmed, call with confirmed: true. Once updated, return a short confirmation.

Delete driver

Use this when the dispatcher explicitly asks to permanently delete exactly one driver from their private Load Nova workspace. For two or more drivers, use delete_drivers once instead of making repeated delete_driver calls. If the dispatcher already confirmed this deletion in the conversation, call immediately with confirmed: true; do not ask for a special confirmation phrase. A retry for an already-absent driver is treated as successful.

Delete multiple drivers

Use this when the dispatcher explicitly asks to permanently delete two or more known drivers. Send all selected driver IDs in one call after one clear confirmation; do not split a bulk request into repeated delete_driver calls. The operation attempts every selected driver, reports partial failures, and treats already-absent drivers as successfully deleted for safe retries.

Dispatch load

Use this only when the dispatcher explicitly asks to assign and activate one real load/route for one driver. Populate every known route field from the conversation or prior tool results: full stops and appointment windows, load ID/reference, rate, equipment, commodity/weight, broker context, and notes. Never invent missing operational facts. Before writing, Load Nova recalculates the route and requires at least 80% route completeness; if the result is below threshold, ask only for the returned m

Compare routes

Compares multiple route choices side-by-side. Present the comparison in a clean, concise markdown table comparing miles, hours, and warnings. Do not write long descriptive paragraphs.

Check driver fit

Use this after list_drivers once the dispatcher has selected a driver by name or reference and the load stops are known. Resolve the internal driverId yourself from prior driver context; do not make the dispatcher copy UUIDs. Evaluates if that driver can cover a specific load. Output the compatibility result (e.g. 'FIT' or 'NOT A FIT' with reasons) in a short, bulleted list of 2-3 items maximum.