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

mcp-lnav-canbus

by baxtheman
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

get_statistics

Generate statistical analysis of CAN bus traffic, including frequency, timing, load, errors, or summary. Optionally filter by CAN ID and time interval.

Instructions

Generate statistical analysis of CAN bus traffic.

Args: stat_type: Type of statistics ("frequency", "timing", "load", "errors", "summary") interval: Time interval for aggregation (e.g., '1s', '100ms') can_id: Optional CAN ID to filter statistics session_id: Session identifier

Returns: Statistical data

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": {
      "stat_type": "<stat_type>"
    },
    "name": "get_statistics"
  }
}

Input Schema

NameRequiredDescriptionDefault
can_idNo
intervalNo
stat_typeYes
session_idNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description must carry the burden of behavioral disclosure. It only says 'Generate statistical analysis' and 'Returns: Statistical data' without detailing side effects, dependencies on an open session, or whether this is a read-only operation. The lack of any behavioral caveats leaves significant transparency gaps.

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?

The description is well-structured: a clear opening sentence followed by a parameter list and a return line. It is not overly verbose, but the 'Returns: Statistical data' line is vague and adds little. Overall, the structure is efficient and avoids unnecessary fluff.

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?

With an output schema present, the vague return statement is acceptable, but the description lacks important context like whether a session must already be open, how the statistics relate to message queries, and when to choose this over sibling tools. It covers parameters adequately but leaves usage context incomplete.

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?

The description compensates for the 0% schema coverage by explaining stat_type with example values, interval with formats, can_id as an optional filter, and session_id as an identifier. However, it does not elaborate on what each stat_type produces, the exact interval format, or the role of session_id beyond 'identifier', so the added meaning is partial.

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

Purpose4/5

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

The description clearly states 'Generate statistical analysis of CAN bus traffic' — a specific verb and resource. However, it does not explicitly differentiate from sibling tools like analyze_payload_noise or find_errors, which could also involve statistical analysis, so it misses the top score for sibling distinction.

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?

No guidance is given on when to use this tool versus alternatives. The description simply lists arguments and a generic return. There is no mention of context, exclusions, or prerequisites, so the agent gets no help deciding between this and other analysis tools.

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