Cariot MCP Server
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ID_TOKEN | No | Cariot ID token for authentication | |
| API_ACCESS_KEY | No | Cariot API access key (used with API_ACCESS_SECRET) | |
| CARIOT_LOG_LEVEL | No | Logging level (debug, info, warn, error) | info |
| API_ACCESS_SECRET | No | Cariot API access secret (used with API_ACCESS_KEY) |
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 |
|---|---|
| analyze_alcohol_checksA | Analyzes alcohol check results from daily reports. Shows check status (before/middle/after), violations, check rate, and check statistics for drivers within a specified date range. Check rate is calculated based on whether both before and after checks are performed when driving (for past dates) or at least before check is performed (for current date). / 日報からアルコールチェック結果を分析します。指定された日付範囲内のドライバーのチェック状況(前/中/後)、違反、チェック率、およびチェック統計を表示します。チェック率は、運転時に乗車前と乗車後の両方のチェックが実施されているか(前日以前)、または少なくとも乗車前チェックが実施されているか(当日)に基づいて計算されます。 |
| generate_chart_configA | Generates Chart.js configuration data based on input data. Supports bar, line, pie, doughnut, radar, and polarArea chart types. Returns a ChartConfiguration object that can be used directly with Chart.js. IMPORTANT: When using this tool, you MUST embed the EXACT generated ChartConfiguration object in your final response WITHOUT any code block markers (no |
| get_daily_reportC | Retrieves a detailed daily report for a specific date and driver. / 指定された日付とドライバーの日報詳細を取得します。 |
| get_daily_reportsB | Retrieves a list of daily reports for all drivers within a specified date range. / 指定された日付範囲内の全ドライバーの日報をリストで取得します。 |
| get_driversC | Retrieves a list of all drivers' information. / 全ドライバーの情報をリストで取得します。 |
| get_realtimeC | Retrieves real-time information for the specified driver or vehicle. / 指定したドライバーまたは車両のリアルタイム情報を取得します。 |
| get_vehiclesC | Retrieves a list of all vehicles' information. / 全車両の情報をリストで取得します。 |
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 7 tools
Each tool targets a distinct aspect of fleet management: drivers, vehicles, daily reports (singular/plural), real-time info, alcohol check analysis, and chart generation. The only potential confusion is between get_daily_report and get_daily_reports, but the singular/plural distinction is clear.
Most tools use the 'get_' prefix consistently, but 'analyze_alcohol_checks' and 'generate_chart_config' break the pattern with different verbs. While readable, the mix of verb styles is inconsistent.
With 7 tools, the server is well-scoped for a fleet data retrieval and analysis domain. Each tool serves a clear purpose without being excessive or insufficient.
The tool set covers core read operations (drivers, vehicles, reports, real-time) and adds analysis (alcohol checks, chart config). However, there are no write operations (e.g., create/update drivers, submit reports), which may limit agents performing management tasks.