Skip to main content
Glama

embedded-eda

can_bus_decode

Decode candump/Lawicel/CSV CAN & CAN-FD frames, extract arbitration IDs (11/29-bit), DLC, bitfield payloads, and OBD-II PIDs.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "can_bus_decode"
  }
}

Input Schema

NameRequiredDescriptionDefault
textNocandump log lines e.g. "(1700000.0) can0 7DF#02010C0000000000".
filePathNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations supplied, the description carries the full disclosure burden. It does say what gets extracted (IDs, DLC, payloads, PIDs), which is useful behavioral context beyond a bare 'decode' claim, but it omits how malformed lines are treated, whether both inputs can be supplied at once, and what the result structure looks like.

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 dense sentence with the verb and formats front-loaded and no filler. It is efficient, though the enumeration of extracted fields makes it slightly list-like rather than guiding.

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

Completeness3/5

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

For a two-parameter tool with no output schema, the description should say what comes back and how the two inputs relate; it only gestures at outputs via the extracted-field list. An agent can invoke it, but must guess about input precedence and error behavior.

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

Parameters3/5

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

Schema coverage is 50%: text carries an example, filePath carries nothing. The description partially compensates by naming candump/Lawicel/CSV as accepted content for the input, which is meaning beyond the schema, but it never clarifies that text and filePath are alternative sources for the same payload.

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?

Names a specific verb (Decode) plus the exact input dialects (candump/Lawicel/CSV) and frame families (CAN & CAN-FD), and enumerates the extracted artifacts (arbitration IDs 11/29-bit, DLC, bitfield payloads, OBD-II PIDs). This clearly separates it from siblings like elf_crash_backtrace_decode or logic_trace_decode_wavedrom, which operate on entirely different input formats.

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 implied by the named input formats: an agent knows to call it when holding candump/Lawicel/CSV logs. However, there is no explicit statement of when to prefer it, no guidance on choosing between the text and filePath inputs, and no note on what it does not handle (e.g., raw binary socketcan captures).

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources