Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
CAN_MCP_WORKSPACE_ROOTNoOverrides the workspace root that file access is sandboxed to. Defaults to the current working directory the server is launched in.

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

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
inspect_database_summaryC

Protocol type, baudrate, ECU/message/signal counts, and node matrix.

search_databaseB

Case-insensitive fuzzy/substring search across messages, signals, IDs, units, comments, and value tables.

visualize_frame_layoutC

ASCII bit/byte grid showing exact Intel/Motorola signal occupancy for one frame.

validate_database_integrityC

Detect bit overlaps, DLC violations, invalid DLC sizes, duplicate names, and bad min/max/scale.

manage_ecu_nodeB

Add, rename, or delete an ECU node (BU_), updating sender/receiver references.

upsert_dbc_messageC

Create or update a CAN/CAN FD frame, writing GenMsgCycleTime and VFrameFormat attributes.

delete_dbc_messageC

Remove a frame cleanly from the database.

add_or_update_signalC

Create or update a signal; auto_pack=True finds the first free bit block. Rejects bit-overlapping writes.

delete_dbc_signalC

Delete a signal and its associated value table/attribute entries.

generate_database_from_templateB

Generate a clean-room baseline, J1939, CANopen CiA301, or UDS/ISO-TP skeleton .dbc from scratch.

convert_database_formatC

Convert between .dbc/.dbf/.arxml/.kcd/.sym/.xlsx (via canmatrix) and report any attribute loss.

diff_databasesB

Structured engineering changelog between two databases of any supported format: added/removed messages and signals, bit shifts, scaling/offset changes, and cycle-time changes.

summarize_trace_logA

Stream a .asc/.blf/.trc/.log/.csv/.parquet trace and return duration, frame/error counts, channels, and a per-arbitration-ID summary table (count, Δt stats, DLC, payload entropy).

query_decoded_signalsB

Decode requested signals across a trace; aggregation='summary' returns min/max/mean/std/anomalies plus a downsampled time series, otherwise up to max_rows raw decoded rows.

filter_and_export_traceB

Stream-filter a trace by arbitration ID, time range, and/or a decoded signal_condition expression, writing matches to .blf/.asc/.trc/.log/.csv/.parquet.

extract_uds_diagnostic_transcriptC

Reassemble ISO-TP (SF/FF/FC/CF) diagnostic sessions and decode UDS requests/responses, NRCs, and security-access lockouts.

reassemble_j1939_multipacketC

Reassemble J1939 BAM/CMDT transport-protocol sessions (PGN 0xEC00/0xEB00) into complete multi-byte PGN payloads.

analyze_bus_health_and_faultsB

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.

reverse_engineer_unknown_framesB

Classify undocumented payload bitfields (constant masks, alive counters, checksum candidates, continuous physical signals, discrete flags) and emit a draft candidate DBC.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

B3.2/5.0

Scored across 19 tools

Disambiguation5/5

The tools target clearly distinct resources and actions: database inspection/search, message/signal/ECU editing, format conversion, trace summarization/query/export, diagnostics, and reverse engineering. Overlaps such as summarize_trace_log vs analyze_bus_health_and_faults and query_decoded_signals vs filter_and_export_trace are separated by clear output and purpose differences.

Naming Consistency4/5

All names use consistent snake_case and are generally verb_noun oriented, which makes them predictable. Minor inconsistency exists in operation vocabulary and granularity, e.g. upsert_dbc_message vs add_or_update_signal, and manage_ecu_node bundles add/rename/delete while message and signal lifecycle operations are split.

Tool Count4/5

Nineteen tools is slightly heavy for the stated scope, but the domain spans database engineering, trace analysis, diagnostics, and reverse engineering, so each tool has a plausible role. It is not inflated with redundant or vague operations.

Completeness4/5

The surface covers database creation, inspection, editing, validation, conversion, diffing, trace analysis/export, UDS/J1939 decoding, health diagnostics, and reverse engineering. Minor gaps remain around direct detailed read/get operations, explicit load/save database lifecycle, and full editing of value tables or arbitrary attributes.