Partialtruckload

Server Health

Returns MCP server health and current UTC timestamp.

Cost Calc Create Truck

Create a new truck for the user's carrier. After calling, follow assistant_instructions to guide the user through filling in cost inputs step by step — do NOT ask for all fields at once. NEVER mention tool names or internal identifiers to the user.

Cost Calc List Trucks

List trucks the user can run cost calculations on. Call this FIRST when the user wants to use the cost calculator. Present results as a clean numbered list and help the user pick one — do NOT dump raw data. NEVER mention tool names or internal identifiers to the user.

Cost Calc Get Context

Load a truck's full cost context and baseline. IMPORTANT: after calling, follow the assistant_instructions in the response to present a friendly cost summary. Check missing_inputs and guide the user to fill gaps before generating scenarios. NEVER mention tool names or internal identifiers to the user.

Cost Calc Increment Usage

Track analytics: increment usage counter when user opens the calculator for a truck. Call once after loading a truck's cost context. This is invisible to the user — do NOT mention it.

Cost Calc Update Truck Inputs

Change one or more cost assumptions and get recalculated baseline. After calling, confirm the changes conversationally and suggest next steps per assistant_instructions. NEVER mention tool names or internal identifiers to the user.

Cost Calc Update Fuel Price

Update the carrier-wide fuel price per gallon and recalculate all truck costs. This affects ALL trucks for the carrier. NEVER mention tool names or internal identifiers to the user.

Cost Calc Generate Scenarios

Generate a what-if comparison table showing cost, revenue and profit at different weekly mileage levels. IMPORTANT: present the result as a formatted table, share the insights, and then offer next steps per assistant_instructions. NEVER mention tool names or internal identifiers to the user.

Load Add Preview

Validate and preview a load before creation. Use this whenever the user provides new/updated shipment details. This tool resolves pickup/dropoff city or zipcode to real records, normalizes common date/time mistakes, parses and validates items, checks equipment against carrier availability, calculates distance and totals, and returns a human-ready preview plus warnings/missing fields. The preview can be called multiple times as user edits data. Output includes `preview`, `resolved_data` (for conf

Load Add Confirm

Create the load after the user has reviewed and confirmed the preview. Requires resolved pickup/dropoff city and zipcode IDs, a positive total price, a non-zero equipment ID, and at least one item with quantity, weight, and length, width, and height (all greater than zero). ONLY call after the user explicitly confirms AND the previous preview had `ready_to_confirm: true` (no blocking issues). Pass the same item data the user verified — do NOT fabricate fields. After calling, follow assistant_ins