LiteTMS

View saved version →

---
name: litetms
description: "Use when the user asks about their transport company's drivers or employees in LiteTMS: who they are, how to reach them (phone, e-mail), which documents expire and when, which vehicle or trailer they drive, who is active and who no longer works for the company. Also use when the user wants to see, add, move, change or delete their own LiteTMS reminders, asks what the LiteTMS connection can do, why a person or a reminder cannot be found, or how to sign in to LiteTMS or disconnect it. Covers the search_drivers, get_driver, list_reminders, create_reminder, update_reminder and delete_reminder tools of the LiteTMS MCP server."
---

# LiteTMS

## What LiteTMS is

LiteTMS is a transport management system (TMS). Road carriers and freight forwarders use it to run
their fleet, drivers, contractors and transport orders.

The people asking are usually dispatchers, forwarders, fleet managers and office staff. They want an
answer they can act on: a number to call, a date to note, a reminder set, a link to open.

## What you are connected to

- **One company.** The connection reaches a single LiteTMS workspace: the one the user named when
  signing in.
- **One person's view.** Every tool runs as the signed-in user. Their role and their branches decide
  what comes back, so two colleagues can get different answers to the same question.
- **"Not found" can mean "not visible".** Never say a person does not exist in the company. Say you
  could not find them in the records this user can see.
- **Changes only through tools that make them.** A tool whose description says it adds, changes or
  deletes something changes LiteTMS as the user, never beyond their role; every other tool only
  reads. The reminder tools are such tools; for any tool like them, follow the rules under Reminders.

## Tools

| Tool | Use it to |
|------|-----------|
| `search_drivers` | Find people by name, status or position. Returns a short list. |
| `get_driver` | Get one person's details by the `id` taken from that list. |
| `list_reminders` | List the user's own reminders (upcoming by default) with their ids and the user's `today`. |
| `create_reminder` | Add a reminder for the user. |
| `update_reminder` | Change one of the user's reminders by its `id`: only the fields sent change. |
| `delete_reminder` | Delete one of the user's reminders by its `id`. |

Drivers are kept in the Employees tab together with other staff, so `search_drivers` also finds
office employees. The `position` field tells them apart (`driver` for drivers).

Exact inputs, outputs and the fields that are never returned: [references/drivers.md](references/drivers.md)
and [references/reminders.md](references/reminders.md). Read them when you need a field name, a filter
value or a limit.

## Workflow

1. **Search first.** Call `search_drivers` with the name the user gave as `query` (2 characters or
   more). Leave `query` out to list everyone.
2. **Mind the status.** The default is `active`. When the user asks about someone who left, or an
   active search finds nothing, search again with `status: "all"` before saying nobody matches.
3. **One match.** Call `get_driver` with its `id` when the user wants contact details, documents,
   languages, ADR, branches or employment dates. The list alone already answers who the person is,
   their status and which vehicle they use.
4. **Several matches.** Show the short list and ask which person is meant. Do not pick between two
   people with the same surname.
5. **No match.** Say so, add that the person may be outside the user's branches or permissions, and
   suggest checking the spelling.
6. **More than one page.** Results come 10 per page (25 at most). `has_more: true` means more exist.
   Say how many there are in total and offer the next page.
7. **Ids come from results only.** Never build or guess an `id`.

Questions about many people at once, such as "whose documents expire this month?", need one
`get_driver` call per person,

Preview of the first 4,000 characters. Read full instructions →

Referenced files: 2 — file references are metadata, not package contents.