fleetsync-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| FLEETSYNC_API_KEY | Yes | Your FleetSync API key | |
| FLEETSYNC_BASE_URL | No | The base URL of the FleetSync API (default: https://api.fleetsync.io/v2) | https://api.fleetsync.io/v2 |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| fleetsync_get_orderA | Get a FleetSync order by its number. Returns order details including status, client, address, delivery date, driver, and proof of delivery info. |
| fleetsync_orders_by_dateA | Get all FleetSync orders for a specific date. Returns list of orders scheduled for that day with their statuses. |
| fleetsync_orders_by_routeA | Get all FleetSync orders assigned to a specific route by its code. |
| fleetsync_orders_status_changesA | Get FleetSync orders that had status changes after a specific date/time. Useful for checking recently delivered/updated orders. Date format: YYYY-MM-DDTHH:mm:ss. Minimum: UTC - 1 day. |
| fleetsync_order_historyA | Get the history of a FleetSync order (last 25 entries). Useful for tracking changes and re-deliveries. |
| fleetsync_create_orderA | Create a new unscheduled order in FleetSync. Requires: Number (max 50 chars), Client, Address, Date (YYYY-MM-DD). Optional: Phone, Email, Note. |
| fleetsync_update_orderA | Update an existing FleetSync order. Requires: Number. Optional fields to update: Client, Address, Phone, Email, Date, Note. |
| fleetsync_delete_orderA | Delete a FleetSync order by its number. This action is irreversible. |
| fleetsync_orders_by_route_dateA | Get all FleetSync orders for a specific date grouped by their assigned routes. |
| fleetsync_get_routesA | Get all FleetSync routes. Returns a list of all route summaries. |
| fleetsync_routes_by_dateA | Get all FleetSync routes for a specific date. Returns route details including driver, status, and order count. |
| fleetsync_get_routeA | Get a specific FleetSync route by its code. Returns route details, driver assignment, orders, and status. |
| fleetsync_create_routeA | Create a new route in FleetSync. Requires Code and Date. Optional: DriverName, DriverVehicle, Depot, Orders. Query options: update, updateAddressGps, mergeAddresses. |
| fleetsync_update_routeB | Update an existing FleetSync route. Requires Code. Optional: Date, DriverName, DriverVehicle, Depot, Orders. Query options: update, updateAddressGps, mergeAddresses. |
| fleetsync_delete_routeA | Delete a FleetSync route by its code. This action is irreversible. |
| fleetsync_analyze_route_distancesA | Analyze distances between consecutive orders in a route. Flags order pairs exceeding the distance threshold. Useful for diagnosing poorly optimized routes. |
| fleetsync_get_driversA | Get all FleetSync drivers. Returns list of drivers with their names, vehicles, phones, and active status. |
| fleetsync_testA | Test FleetSync API authentication and check rate limits. |
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 18 tools
Most tools are clearly distinct, but the overlapping query tools (orders_by_date vs orders_by_route_date, get_routes vs routes_by_date) could cause misselection if an agent doesn't read descriptions carefully. Each tool has a unique filter or aggregation purpose, so ambiguity is low but not absent.
All tools share the fleetsync_ prefix, but the verb_noun pattern is broken by query-style names like orders_by_date, orders_status_changes, order_history, and routes_by_date. This mixed convention reduces predictability, though the domain terms keep the names readable.
At 18 tools, the set is slightly over the ideal 3-15 range, but the count is justified by full CRUD for both orders and routes plus multiple query views and an analytics tool. Each tool has a clear purpose, so it feels slightly heavy rather than bloated.
The set covers CRUD for orders and routes, along with useful queries and distance analysis. However, order status cannot be updated (only read), route status is not manageable, and driver tools are limited to listing. This leaves significant gaps for agents needing to update delivery progress or assignments.