Skip to main content
Glama
OpenCyber Harness
by mitkox

oc_canbusload

Destructive

Runs the canbusload CAN bus load analyzer with supplied argv tokens in an engagement namespace, executing directly without shell parsing for safe, reproducible automotive network diagnostics.

Instructions

Run canbusload from the OpenCyber automotive toolkit. The container executes canbusload directly with the supplied argv tokens; shell parsing is never used. 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_canbusload"
  }
}

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

A3.7/5.0
Behavior4/5

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

The annotations already declare this as destructive, open-world, non-idempotent, and not read-only. The description adds meaningful execution behavior beyond that: the container executes canbusload directly with argv tokens and never uses shell parsing, and it specifies namespace/path expectations. It does not elaborate on destructive effects or rate/auth constraints, but it substantially supplements the annotations.

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 three tightly written sentences. It front-loads the action, then explains execution semantics, then path/namespace rules, with no filler or repetition.

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?

For a destructive open-world CLI wrapper with four parameters and an output schema, the description covers invocation mechanics and path scoping reasonably well. It still omits stdin semantics and any indication of what canbusload itself does or produces beyond the binary name, so it is adequate but 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?

Schema description coverage is 0%, so the description must carry the burden. It clarifies that 'arguments' are argv tokens, that relative paths should be used for engagement artifacts, and that execution is scoped to the selected engagement namespace. It does not explain the 'stdin' parameter at all, leaving a notable gap for a four-parameter tool.

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 uses a specific verb, 'Run', and names the exact binary, 'canbusload', with toolkit context. It is clear what the tool does, though it does not distinguish it from the many sibling wrapper tools beyond the binary name.

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 operational context by saying it runs from the selected engagement namespace and to use relative paths for engagement artifacts. However, it provides no explicit when-to-use guidance, exclusions, or guidance on choosing among the many sibling 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