Skip to main content
Glama

analyze_bus_health_and_faults

Diagnose CAN bus load spikes, error storms, Bus-Off, timing jitter, missing frames, babbling nodes, and alive-counter skips or freezes, with root-cause advisories.

Instructions

Diagnose bus load/microbursts, error storms & Bus-Off transitions, cycle-time jitter/missing-frame/babbling-node faults, and alive-counter skips/freezes, with root-cause advisories.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "log_path": "<log_path>"
    },
    "name": "analyze_bus_health_and_faults"
  }
}

Input Schema

NameRequiredDescriptionDefault
dbc_pathNo
log_pathYes
fd_data_baudrateNo
nominal_baudrateNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description carries the full burden. It does disclose the analysis classes and that it emits root-cause advisories, which is meaningful behavioral context, but it never states that the operation is read-only, how expensive the analysis is, or that certain checks depend on a DBC or correct baudrates.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single sentence with the action verb front-loaded and no filler; the dense fault enumeration is substantive rather than padding. It is slightly list-heavy to scan, but every clause names a distinct capability.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a multi-fault analysis tool with four undocumented parameters, no annotations, and no output schema, the description leaves major gaps: the DBC dependency for cycle-time and alive-counter checks, the meaning of the baudrate defaults, and any sense of result structure are all absent. An agent could call it but not predict its behavior or interpret gaps.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

All four parameters have 0% schema description coverage, so the description must compensate and does not mention log_path, dbc_path, nominal_baudrate, or fd_data_baudrate at all. The baudrate parameters are especially critical for bus-load and microburst computation, yet their role and units are unexplained anywhere.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Uses a specific verb ("Diagnose") plus a detailed enumeration of what is diagnosed: bus load/microbursts, error storms, Bus-Off, cycle-time jitter, missing frames, babbling nodes, alive-counter skips/freezes, and root-cause advisories. This taxonomy clearly separates it from siblings like summarize_trace_log or query_decoded_signals, which report rather than diagnose faults.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied by the fault list; there is no explicit statement of when to reach for this over summarize_trace_log or filter_and_export_trace, and no prerequisites or exclusions are given. An agent can infer it is for fault triage on a log, but nothing confirms that.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.