Skip to main content
Glama
OpenCyber Harness
by mitkox

oc_cansniffer

Destructive

Displays changing CAN bus frames and payloads in a selected engagement namespace, enabling live vehicle bus traffic inspection and relative-path access to engagement artifacts.

Instructions

Display changing CAN bus frames and payloads. Runs from the selected engagement namespace; use relative paths for engagement artifacts.

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": {
      "engagement_id": "<engagement_id>",
      "arguments": "<arguments>"
    },
    "name": "oc_cansniffer"
  }
}

Input Schema

NameRequiredDescriptionDefault
stdinNo
argumentsYes
engagement_idYes
working_directoryNo.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.7/5.0
Behavior2/5

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

Annotations already declare destructiveHint=true, openWorldHint=true, and idempotentHint=false, so the safety profile is covered. The description adds only namespace scoping and relative-path handling; it never explains that the tool wraps a CLI executable driven by the "arguments" array, what that process may touch, or why a "display" tool is flagged destructive. That unexplained tension leaves real behavioral ambiguity.

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?

Two short sentences, front-loaded with the purpose and followed by the invocation constraint, with no filler. It is efficient, though the terseness leaves the schema gaps unaddressed.

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?

An output schema exists, so return values need not be described. However, for a four-parameter wrapper with 0% schema coverage, two required parameters, and a destructive annotation, the definition is too thin to let an agent construct a correct call without guessing at the argument format.

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?

Schema description coverage is 0% across four parameters, so the description must carry the burden and largely does not. It gives partial meaning to engagement_id (namespace selection) and working_directory (relative artifact paths), but says nothing about the required "arguments" array, which is clearly the CLI argument vector, nor about "stdin".

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?

"Display changing CAN bus frames and payloads" gives a concrete verb (display) and resource (CAN bus frames/payloads), which tells an agent this is a live monitoring/sniffing operation rather than a one-shot capture tool. It does not connect itself to any sibling, but the resource is distinctive enough that disambiguation is not really needed.

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?

There is no guidance on when to prefer this over an alternative (e.g., a capture-to-file or log-analysis tool), no prerequisites (CAN interface, hardware availability), and no stated exclusions. The only operational note, running from the selected engagement namespace with relative paths, is about invocation context, not selection.

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