Skip to main content
Glama
OpenCyber Harness
by mitkox

oc_isotpsend

Destructive

Send ISO-TP diagnostic payloads over CAN within an engagement namespace to test ECU communication; use relative paths for engagement artifacts.

Instructions

Send ISO-TP (ISO 15765-2) diagnostic payloads over CAN. 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_isotpsend"
  }
}

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.9/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, openWorldHint=true, idempotentHint=false and readOnlyHint=false, so the safety profile is covered. The description usefully adds the engagement-namespace scoping and relative-path convention, but says nothing about what the send affects on the bus, whether it can brick an ECU, or how raw arguments are interpreted.

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 core action and followed by scoping constraints. Nothing is redundant, though the phrase 'engagement artifacts' is slightly vague for the space it occupies.

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 tool with a raw CLI passthrough parameter and 0% schema coverage, the description is too thin; an agent cannot tell how to structure 'arguments' or what side effects to expect. The existence of an output schema excuses it from explaining return values, but the input-side gap remains large.

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 it does not. It never explains that 'arguments' is a raw CLI argument vector, nor what 'stdin' and 'working_directory' do; only a vague nod to relative paths hints at working_directory.

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 states a specific verb and resource: 'Send ISO-TP (ISO 15765-2) diagnostic payloads over CAN', including the protocol standard, so an agent knows exactly what domain this operates in. It does not distinguish itself from any related CAN/diagnostic sibling, but the core action is unambiguous.

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 use this versus alternatives, no prerequisites (CAN interface up, paired receiver like an isotp receive tool), and no exclusions. The only operational note is that it runs inside the engagement namespace and expects relative paths, which is execution context rather than usage guidance.

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