Skip to main content
Glama
OpenCyber Harness
by mitkox

oc_cansend

Destructive

Send a single CAN frame over a SocketCAN interface within a selected engagement namespace, using relative paths for engagement artifacts.

Instructions

Send one CAN frame on a SocketCAN interface. 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_cansend"
  }
}

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.8/5.0
Behavior2/5

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

The annotations already declare destructiveHint=true, openWorldHint=true, idempotentHint=false and readOnlyHint=false, so the safety profile is covered structurally. The description adds the engagement-namespace and relative-path context, which is useful. However, it says nothing about likely failure modes (missing interface, permissions or CAP_NET_RAW), and it doesn't clarify that 'arguments' is a shell-level passthrough to the CLI, so the agent doesn't know what it is actually emitting.

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 action and followed by the execution-context note. Nothing is padded. Density is good, though at this length the brevity trades off against needed detail.

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?

An output schema exists, so return values need no explanation. For a destructive, open-world tool, the definition should still say what the arguments array represents and what must be in place before it will work. The engagement/working-directory guidance helps, but the core invocation contract remains undocumented.

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 carries the full burden for four parameters and fails to do so. Only engagement_id is indirectly explained by the 'engagement namespace' sentence and working_directory by the relative paths note. The most important parameter, the 'arguments' string array that presumably forms the cansend command line, is completely undefined, and stdin is never mentioned.

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: 'Send one CAN frame on a SocketCAN interface.' An agent knows immediately this is the raw frame-injection tool rather than a scan or monitor tool. What is unclear is that the frame payload is supplied through the generic 'arguments' passthrough array, so a reader cannot tell how the frame is expressed.

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 states no conditions for use and no alternatives. It does not mention that a SocketCAN interface (for example can0) must already exist and be up, or when to prefer a monitor or scan tool instead. The only practical guidance is the note about relative paths for engagement artifacts.

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