Skip to main content
Glama
OpenCyber Harness
by mitkox

oc_candump

Destructive

Capture CAN bus frames from a SocketCAN interface into an engagement artifact, using relative paths within the selected engagement namespace.

Instructions

Capture CAN bus frames from a SocketCAN interface into an engagement artifact. 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_candump"
  }
}

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

B3.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=true, openWorldHint=true and non-idempotent, so the write/side-effect profile is covered structurally; the description adds that output lands in an engagement artifact via the engagement namespace. It omits the most important behavioral trait for an agent: candump normally streams continuously, so the description should say whether it blocks, how long it runs, and how to bound or stop it.

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 compact sentences with the action front-loaded and the namespace/path constraint following. No filler, though the brevity comes partly at the cost of the missing operational detail rather than being pure efficiency.

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?

For a destructive, open-world capture tool with four undocumented parameters and an opaque CLI-argument passthrough, the definition is thin. The output schema covers return values, but the agent is left without knowledge of duration/stop semantics, privilege requirements, or how to shape the capture via the arguments array.

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%, so the description must carry parameter meaning and largely does not. In particular the 'arguments' array is an opaque string passthrough to the candump CLI — the description never says that, nor names expected flags (interface, frame count, filters), and only indirectly implies working_directory behavior through the relative-path note.

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 names a specific verb and resource — capture CAN bus frames from a SocketCAN interface — plus the destination (an engagement artifact). It is immediately clear what the tool does, though it does not differentiate itself from any sibling or state which interface/target selection it expects.

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?

It gives practical invocation context ('runs from the selected engagement namespace; use relative paths for engagement artifacts'), which is genuinely useful for path handling. However, it gives no when-to-use versus alternatives, and no preconditions such as root privileges, an interface already brought up, or bitrate configuration.

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