Tool arsenal
The categories of tools fOS can invoke, mapped to the mission loop — fleet, load search & bidding, chain economics, market intelligence, outreach, live negotiation, workspace (email/calendar/drive), and session/context. A per-tool reference generated from the contract registry follows.
fOS's capabilities are its tools — discrete, typed actions and reads it can invoke. They
are curated by the inclusion principle:
a tool exists only if it moves a deal through the loop, produces
a read that changes the next action, is a real reference table, or is required plumbing. This
page catalogs the categories; each links to a per-tool table verified against the tool
contract registry (packages/services/src/ai-tools/contracts/).
Categories, mapped to the loop
| Category | Loop stage | What it does |
|---|---|---|
| Fleet & vehicles | find | The carrier's trucks — status, location, and which loads fit which vehicle. |
| Load search & bidding | find · bid | Find loads and act on them — direct offers and exchange bids. |
| Chain economics | price | The cost-of-record read — a chain's real per-leg P&L. |
| Market intelligence | price | Market prices from APEX plus benchmark reference tables. |
| Outreach & CRM | negotiate · learn | The shipper relationship — profiles, briefings, and logging interactions. |
| Live negotiation | negotiate | Real-time deal-making on a call — margin checks, status, escalation. |
| Workspace | negotiate · execute | Acting in the user's Google/Microsoft workspace — mail, calendar, files. |
| Session & context | plumbing | Identity, org scoping, exports, and connecting integrations. |
How to read a tool table
Each per-category page lists its tools with two flags that come straight from the contract registry:
- Type — Read (a query; safe to call freely) or Action (changes state; may pause for confirmation on the money path — see Guardrails).
- MCP — whether the tool is exposed to external assistants. Reads are broadly exposed; many writes are gated or withheld (see Surfaces).
A few high-stakes tools — confirm_win, the live-negotiation tools, connect_integration, and
get_price_estimate — carry extra prose on their category page because their behavior is subtle.
The cost-of-record versus market distinction
Two categories touch money, and the distinction is deliberate:
- Chain economics (
get_chain_economics) is the cost-of-record — the real per-leg P&L from the cost engine. This is the number to trust for a specific chain. - Market intelligence (
get_price_estimate) is the market — what the lane pays, from APEX. Its benchmark tables (fuel, driver rates) are reference rows, not the cost of any specific chain.
fOS never uses a market or benchmark tool to stand in for the cost-of-record. See Cost grounding.
Connecting fOS
To drive these tools from an external assistant (Claude, ChatGPT) over MCP or REST, see the fOS Agent API.
Connect an assistant
Drive fOS from an external AI assistant — Claude, ChatGPT, or any MCP client — by pointing it at the fOS Agent API at mcp.tovr.eu and authenticating with an API key or the OAuth browser flow.
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.