Skip to main content
Glama
Sign In
mcp-lnav-canbus

mcp-lnav-canbus

by baxtheman
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

open_can_log

Open a Kvaser CAN bus log file to begin analysis, returning file details and session information in a new or existing session.

Instructions

Open a Kvaser CAN bus log file in the current session.

Args: file_path: Path to the Kvaser CAN log file session_id: Optional session identifier (auto-generated if not provided)

Returns: File information and session details

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": {
      "file_path": "<file_path>"
    },
    "name": "open_can_log"
  }
}

Input Schema

NameRequiredDescriptionDefault
file_pathYes
session_idNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior2/5

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

With no annotations, the description must disclose behavioral traits. It mentions session_id auto-generation and return of file info, but does not explain side effects like session state modification, error handling, or permission requirements.

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

Conciseness5/5

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

The description is compact, front-loaded with the purpose, and organized with Args and Returns sections. No wasted words.

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?

The tool is simple, and the description covers purpose, parameters, and return info. However, it lacks usage context (e.g., need to open before querying) and behavioral details. The output schema exists, so return details are adequate.

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

Parameters4/5

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

Schema description coverage is 0%, so the description compensates by explaining file_path as a path to Kvaser CAN log and session_id as a optional auto-generated identifier. This adds meaningful context beyond the schema's type/title.

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?

The description uses a specific verb 'Open' with a resource 'Kvaser CAN bus log file' and clarifies it's in the current session. This clearly distinguishes it from sibling tools that query/analyze/extract data.

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

Usage Guidelines2/5

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

The description provides no explicit guidance on when to use this tool vs siblings. It implies it's an entry point ('in the current session') but doesn't state prerequisites or alternatives.

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

Deploy Server

Other Tools