ecuworkbench
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ECU_WORKBENCH_ROOT | Yes | The directory configured to hold ECU artifacts. Tool paths are relative to ECU_WORKBENCH_ROOT. |
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 |
|---|---|
| capabilitiesA | List supported formats, file limits and unavailable ECU operations. |
| inspect_tuneA | Read MSQ metadata and raw constants inside ECU_WORKBENCH_ROOT; do not validate calibration. |
| compare_tunesB | Compare raw MSQ constants with matching firmware signatures and shared units; never write a tune. |
| summarize_logC | Summarize exported plain CSV channels with optional explicit caller-supplied units. |
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 4 tools
Each tool has a clearly distinct purpose: capabilities reports limits, inspect_tune reads metadata/constants, compare_tunes compares two tunes, and summarize_log summarizes CSV logs. There is no meaningful overlap among the actions or resource targets.
All names use snake_case, and three follow a verb_noun pattern. The only deviation is 'capabilities', which is a noun rather than a verb, but it remains readable and predictable as a discovery tool.
Four tools is well scoped for a read-only ECU analysis workbench. Each tool covers a distinct operation, and there are no redundant or filler tools.
The set covers inspection, comparison, log summarization, and capability discovery for a deliberately read-only workflow. A tune/file listing tool might help agents discover available MSQ files, but the explicit no-write/no-validation scope keeps the surface mostly complete.