Skip to main content
Glama
OpenCyber Harness
by mitkox

oc_serial_open

Destructive

Open a raw, persistent serial/UART session on a permitted device and capture a JSONL transcript under hardware/serial/<session_id>.jsonl.

Instructions

Open a raw, persistent serial/UART session on a device passed into the container. Captures a transcript under hardware/serial/<session_id>.jsonl. Device must be a character device under /dev/ttyUSB*, /dev/ttyACM*, /dev/ttyS*, /dev/serial/, /dev/rfcomm*, or /dev/lirc*.

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>",
      "device": "<device>"
    },
    "name": "oc_serial_open"
  }
}

Input Schema

NameRequiredDescriptionDefault
deviceYes
parityNonone
baudrateNo
bytesizeNo
stopbitsNo
engagement_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, readOnlyHint=false, openWorldHint=false, so the mutation profile is known. The description adds real context beyond that: the session is persistent, and a transcript is written to hardware/serial/<session_id>.jsonl. It does not explain why the operation is flagged destructive (e.g. device contention, exclusive locking) or what happens if the device is already in use, so the key behavioral gap remains.

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?

Three sentences, front-loaded with the action and its most decision-relevant constraint, with zero filler. The trailing device-path enumeration is dense but functional; nothing is redundant.

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 not be described. Still, for a stateful, destructive session opener, the description omits the lifecycle contract (that a matching close is required to release the device) and any permission or contention caveats, leaving meaningful gaps for an agent coordinating with oc_serial_read/oc_serial_write/oc_serial_close.

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% across six parameters, so the description must carry the burden, and it only partially does. It adds meaningful format/whitelist semantics for the required 'device' parameter beyond a bare string type, but baudrate, parity, bytesize, stopbits, and engagement_id receive no explanation at all beyond their schema defaults.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Open a raw, persistent serial/UART session') plus the object it acts on ('a device passed into the container'). This clearly distinguishes it from siblings like oc_serial_read, oc_serial_write, and oc_serial_close without the agent needing to open any schema.

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?

The description gives a hard prerequisite (the device must be a character device under one of six listed /dev path families), which is genuine usage guidance. However, it never says when to choose this opener versus oc_serial_list first, nor does it state that the resulting session must subsequently be closed with oc_serial_close. Usage is implied rather than routed.

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