trucksim-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| TRUCKSIM_SOURCE | No | The telemetry source: 'mock' (built-in scripted trip), 'http' (remote game via HTTP feed), 'mmap' (local Windows shared memory), or 'replay' (replay a recorded drive). Defaults to 'mock'. | mock |
| TRUCKSIM_HTTP_URL | No | The URL of the telemetry HTTP server (e.g., http://<game-pc-ip>:25555/api/ets2/telemetry). Only required when TRUCKSIM_SOURCE is set to 'http'. |
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_truck_stateA | Current truck state: speed vs limit, engine, gear, cruise, fuel, damage, lights. The one-call "what's happening right now" snapshot. Works with any configured source (mock/http/mmap). |
| get_navigationA | Routing status: distance and ETA to the destination, posted limit, and whether you're currently speeding. |
| get_fuel_statusA | Fuel level, consumption, estimated range, and whether it's enough to reach the routed destination. |
| get_active_jobA | The current delivery job: cargo, route, pay, deadline, and on-time status. |
| check_speedingA | Are you speeding right now, and by how much over the posted limit? |
| get_eco_scoreA | A 0-100 driving score for this session, with the factors dragging it down. |
| get_trip_summaryA | Rolling trip totals since the server started: distance, time, speeds, fuel, events. |
| get_rest_advisorA | Fatigue guidance based on continuous driving time (EU hours-of-service style). |
| list_recent_eventsA | Recent driving events (speeding, hard braking, collisions, refuels), newest first. |
| get_raw_telemetryA | The full normalized telemetry snapshot as JSON (for power users / debugging). |
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 10 tools
Each tool targets a distinct aspect of the truck state (speed, fuel, navigation, job, etc.), but there is some overlap: get_truck_state includes speed/fuel while check_speeding and get_fuel_status focus on those specifically. Descriptions clarify the focus, so agents can generally select correctly.
Most tools follow a get_ verb pattern, but check_speeding and list_recent_events break the convention with different verbs. This is more than a minor deviation, though still readable and predictable overall.
With 10 tools, the server is well-scoped for a truck telemetry/monitoring purpose. Each tool has a clear role, and none feel redundant or missing at this granularity.
The tool set covers a broad range of truck and driver status (state, navigation, fuel, job, speeding, eco, trip, rest, events, raw data). Missing operations like historical queries or filtered events are minor gaps that most workflows can work around.