fleet-mcp-server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| FLEET_DB | No | Path to the SQLite database file. The database is created and seeded on first run if it does not already exist. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
Tools for answering questions about a vehicle fleet: usage, idling and its fuel cost, engine fault codes and driver safety. All data is simulated. Vehicle ids look like V001; call list_vehicles first if you do not know them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_vehiclesA | List vehicles in the fleet, optionally filtered by depot (Ottawa, Toronto, Montreal). |
| vehicle_summaryA | Usage summary for one vehicle over the last |
| idling_reportA | Rank vehicles by engine idle time over the last |
| active_faultsB | Active engine fault codes across the fleet, most severe first. Optionally filter by severity: low, medium or high. Use this for maintenance triage. |
| driver_safety_scoresA | Driver safety scores (0-100, higher is safer) from harsh-driving and speeding events
per 100 km over the last |
| recent_tripsB | Most recent trips for one vehicle, newest first, with driver, distance, idle minutes, fuel and top speed. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 6 tools
Each tool targets a distinct analytical view: fleet inventory, per-vehicle summary, fleet idle ranking, fleet fault triage, driver safety ranking, and per-vehicle trip detail. Minor overlap exists because vehicle_summary includes idle, fault, and trip metrics that idling_report, active_faults, and recent_trips cover in more depth, but scope and granularity differences keep selection clear.
All names use snake_case and are readable, but the set mixes verb-led names (list_vehicles, recent_trips) with noun-phrase names (vehicle_summary, idling_report, active_faults, driver_safety_scores). The inconsistency is stylistic rather than confusing, so agents can still infer intent.
Six tools is a well-scoped set for a fleet analytics server, with no redundant filler. Each tool maps to a common reporting question.
The read-only analytics surface covers fleet inventory, per-vehicle utilization, idling cost, fault triage, driver safety, and recent trip detail, which are the core queries for this domain. Minor gaps remain, such as a fleet-wide utilization overview or driver/vehicle metadata and maintenance history, but agents can work around them with the existing summaries.