connected-vehicle-health
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SF_PASSWORD | No | Salesforce password for username-password authentication. | |
| SF_USERNAME | No | Salesforce username for username-password authentication. | |
| SF_LOGIN_URL | No | Salesforce login URL, defaults to https://login.salesforce.com. | https://login.salesforce.com |
| SF_TARGET_ORG | No | Salesforce CLI target org alias, defaults to 'vehicleHealth'. | vehicleHealth |
| SF_ACCESS_TOKEN | No | Salesforce access token for OAuth authentication. | |
| SF_INSTANCE_URL | No | Salesforce instance URL for OAuth authentication, e.g. https://yourInstance.salesforce.com. | |
| SF_SECURITY_TOKEN | No | Salesforce security token (optional for username-password auth). | |
| VEHICLE_DATA_SOURCE | No | Data provider backend: 'salesforce' (default) or 'simulator'. | salesforce |
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
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_vehiclesA | Enumerate all vehicles reporting telemetry, with profile and last-seen time. |
| get_vehicle_healthA | Return the overall health score (0–100) and per-domain breakdown for a vehicle. Only domains with supporting data are scored. Optionally filter to specific domains. |
| read_live_pidsA | Snapshot of the latest OBD-II PID / CAN signal values for a vehicle. Provide PID keys, or omit for a default set. |
| get_dtcsB | Return active DTCs for a vehicle, with severity and affected domain. |
| get_parameter_historyA | Return the recent time-series for one PID (most recent |
| decode_dtcB | Explain a diagnostic trouble code: system, likely causes, symptoms, and recommended actions. |
| predict_maintenanceA | Forecast component-level maintenance risks from current signals, DTCs, and domain scores. Returns ranked risks with recommendations. |
| clear_dtcsA | Clear stored and pending DTCs and reset the MIL. Requires confirm=true. Disabled for read-only backends (e.g. Salesforce). |
| send_commandA | Send a remote command to the vehicle (lock, climate, locate, etc.). Requires confirm=true. Disabled for read-only backends (e.g. Salesforce). |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| fleet-summary | Fleet-wide roll-up: each vehicle's overall health score and status. |
| dtc-catalog | Knowledge base of diagnostic trouble codes the platform can decode. |
TDQS
Scored across 9 tools
Each tool has a distinct purpose: vehicle listing, health scoring, DTC management (decode, get, clear), parameter history, live PIDs, maintenance prediction, and remote commands. No overlap.
All tool names follow a consistent verb_noun pattern in snake_case, e.g., list_vehicles, get_dtcs, send_command. No mixing of conventions.
Nine tools is well-scoped for a vehicle health domain covering diagnostics, health monitoring, historical data, live data, predictions, and commands. Not over- or under-tooled.
The tool surface covers the full lifecycle: vehicle discovery, health assessment, DTC handling (get, decode, clear), parameter history, live readings, predictive maintenance, and remote commands. No obvious gaps for the stated purpose.