Fleet & vehicles

fOS tools for the carrier's own trucks — reading fleet status and vehicle detail, finding vehicles near a location, checking which loads fit a vehicle, and posting availability. Verified against the contract registry.

Tools for the carrier's own fleet — where the trucks are, what they are, which loads fit them, and posting their availability. These serve the find stage of the mission loop. See the arsenal overview for how to read the table.

Tool	Type	MCP	Purpose
`get_fleet_status`	Read	✓	Fleet state — vehicles and their effective locations.
`get_vehicle_info`	Read	✓	One vehicle's details, by licence plate.
`search_fleet_location`	Read	✓	Vehicles near a location (bounded search radius).
`get_vehicle_matches`	Read	✓	Which available loads fit a given vehicle.
`check_shipments_vehicle_fit`	Read	✓	Whether specific shipments fit a vehicle.
`get_proposed_chains`	Read	✓	System-built chains for the fleet.
`report_vehicle_available`	Action	✓	Post a truck's availability (where/when it's free).
`bulk_report_vehicles_available`	Action	✗	Bulk availability upload (not meaningful over MCP text).
`subscribe_vehicle_loads`	Action	✗	Standing search — get notified of new loads for a vehicle.
`show_vehicles_on_map`	Read	✗	Web-only map rendering of vehicles.

MCP: ✓ exposed to external assistants; ✗ web-only (UI or upload-driven).

Decision-grade reads here (get_vehicle_matches, check_shipments_vehicle_fit) change the very next action — they tell the dispatcher which load to pursue. From a match, the natural next step is chain economics and then a bid.