Rig management
list_rigs
List all registered rigs with connection status.
Parameters: None
Returns:
get_rig_config
Get connectivity status and hardware summary for one rig.
Parameters:
Exact name of the rig as registered in the control plane.
register_rig
Register a new rig and return its API key.
Parameters:
Unique name for the rig. Letters, numbers, hyphens (e.g.
orin-bench-01).Test runs
list_runs
List recent test runs, optionally filtered by rig.
Parameters:
Filter to runs from this rig. Pass
null for all rigs.Maximum number of runs to return. Max 500.
get_run_summary
Get a full summary of one run including pass rate and duration.
Parameters:
UUID of the run.
run_test_suite
Create a queued run and push it to the connected agent.
Parameters:
Name of the rig to run tests on.
Path to the YAML suite manifest as known to the agent (e.g.
tests/suites/engine_validation.yaml).Optional tag filter — only tests matching at least one tag are run.
Optional suite type filter (e.g.
smoke, regression).run_id for polling.
cancel_run
Cancel a running test suite.
Parameters:
UUID of the run to cancel. Only
running runs can be cancelled.Result inspection
get_results
List test results for a run.
Parameters:
UUID of the run.
Filter by status:
pass, fail, blocked, error, or skip.get_signal_trace
Extract signal samples for a specific signal across the most recent tests in a run.
Searches up to 5 test results. Returns up to 100 samples per test.
Parameters:
UUID of the run.
Signal name as stored in test results (e.g.
EngineData.RPM).describe_failure
Get complete failure context for one test in one run. This is the primary tool for AI failure analysis — it returns everything needed for root-cause analysis in a single call.
Combines: run metadata, error messages, log lines, signal traces (up to 5 signals, 100 samples each).
Parameters:
UUID of the run.
Test ID as declared in the YAML manifest.
Signal and suite introspection
list_signals
Parse a DBC file and return metadata for every signal.
Parameters:
Path to the
.dbc file, relative to the working directory when the MCP server was started.list_tests
Parse a YAML suite manifest and return metadata for every test.
Parameters:
Path to the YAML manifest (e.g.
tests/suites/engine_validation.yaml).AI-assisted tools
generate_test_suite
Scaffold a YAML manifest and Python stubs, optionally with AI-generated assertions.
Parameters:
Snake-case suite name (e.g.
brake_validation).One-sentence description of what the suite validates.
Hardware variant to target.
Directory to write both files.
Manual context: signal names, fault scenarios, integration flows, sensor feeds.
Rig TOML — auto-extracts ECU names, power rails, GPIO presence.
DBC file — auto-extracts all
MessageName.SignalName pairs.Provider override:
anthropic, openai, gemini.analyze_component
Extract the signal interface contract of a C/C++ software component.
Requires pip install 'crucihil[analyze]'.
Parameters:
Path to a
.c/.cpp/.h file or a directory of source files.Label for this component in the output (e.g.
BrakeController).One or more DBC file paths. Merged with TOML-discovered DBCs.
Rig TOML — auto-discovers DBCs from
[rig.definitions], infers interface type from key name.Shim header directories or SWC paths to parse alongside the primary source.
Provider override:
anthropic, openai, gemini.