audit_broker_domain
ChatGPTChecks a broker's email domain for fraud or security risks. Present the audit findings in a very short bulleted list. Clearly state 'PASS' or 'WARNING/FAIL' at the very beginning of your response.
audit_rate_confirmation
ChatGPTAnalyzes 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.
calculate_route
ChatGPTUse this as soon as pickup and dropoff are known and the dispatcher needs deterministic miles, timing, warnings, and assignment blockers. Do not wait for perfect data; report missing appointment, HOS, equipment, or margin checks.
check_driver_fit
ChatGPTUse 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.
compare_routes
ChatGPTCompares 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.
create_driver
ChatGPTCreates a new driver profile in the authenticated dispatcher's private Load Nova workspace after explicit dispatcher confirmation. Driver profile and equipment fields are expected first-party operational business data supplied by the dispatcher for dispatch workflows. If the dispatcher has already answered yes/confirmed the create action in the conversation, call this tool immediately with confirmed: true; do not ask for a special confirmation phrase. Once created, output a short confirmation sentence with the driver name and ID. If registration fails, briefly ask for the correct details in one sentence.
delete_driver
ChatGPTDeletes a driver record from the authenticated dispatcher's private Load Nova workspace after explicit dispatcher confirmation. If the dispatcher has already answered yes/confirmed the deletion in the conversation, call this tool immediately with confirmed: true; do not ask for a special confirmation phrase. Once deleted, output a short confirmation sentence.
dispatch_load
ChatGPTAssigns a route/load to a driver after explicit dispatcher confirmation. If the dispatcher has already answered yes/confirmed the assignment in the conversation, call this tool immediately with confirmed: true; do not ask for a special confirmation phrase. The server will generate an idempotency key when one is not supplied. If successful, output a short confirmation sentence. If it fails, briefly ask for clarification in one sentence.
explain_route
ChatGPTUse this when the dispatcher asks why a route is risky, wants timing/miles/warning reasoning, or needs a plain-language dispatch read before assignment. Prefer calculate_route for fast default answers.
get_driver_details
ChatGPTUse this after the dispatcher names or selects one driver and needs assignment-critical status, equipment, contact, license, and active-route context before comparing route fit.
list_drivers
ChatGPTUse this when the dispatcher needs available driver candidates, wants to start an assignment review from capacity, or asks who can cover a load. Keep broad lists compact and do not fetch each driver detail.
render_dispatcher_card
ChatGPTUse this only when a compatible client supports widget resources and already has final Load Nova structured content. In text-only ChatGPT flows, present Markdown dispatcher cards instead.
start_dispatcher_session
ChatGPTUse this first when a dispatcher is new, asks what Load Nova can do, needs a starting point, or has just connected the app. Returns a compact workflow card with the fastest next prompts and no backend data lookup.
update_driver
ChatGPTEdits driver profile parameters in the authenticated dispatcher's private Load Nova workspace after explicit dispatcher confirmation. Driver profile and equipment fields are expected first-party operational business data used for dispatch workflows. If the dispatcher has already answered yes/confirmed the update in the conversation, call this tool immediately with confirmed: true; do not ask for a special confirmation phrase. Once updated, output a short confirmation sentence with the driver name and ID.