Skip to main content
Glama
OpenCyber Harness
by mitkox

oc_minicom

Destructive

Open and manage interactive serial console sessions for UART devices inside an engagement workspace, using relative paths to access engagement artifacts.

Instructions

Interactive serial console. Prefer oc_serial_open/read/write for agent-driven UART sessions with persisted transcripts. 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_minicom"
  }
}

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

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

Annotations already disclose destructiveHint=true, openWorldHint=true, and non-idempotent behavior, so the safety profile is covered structurally. The description adds real context beyond that — execution from the selected engagement namespace and relative-path conventions for artifacts. It does not explain how stdin interacts with an interactive console or what state the tool may mutate on the target.

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?

Three short sentences, front-loaded with what the tool is and immediately followed by the alternative to prefer. No filler or restatement of the name or annotations.

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, and the namespace/path conventions are covered. However, for an interactive console wrapper whose required argument is arbitrary argv, the description is too thin for an agent to invoke it correctly without guessing.

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, and the description only gestures at working_directory and engagement_id via 'relative paths' and 'selected engagement namespace'. The required 'arguments' array — presumably raw minicom CLI flags — and 'stdin' are entirely unexplained, leaving the most consequential parameters undocumented in both places.

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?

States a specific resource and mode: 'Interactive serial console,' which an agent can distinguish from the programmatic serial siblings. It stops short of saying that it is a raw minicom wrapper driven by pass-through argv, so the exact operation performed with the supplied arguments is left implicit.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly names the alternatives ('Prefer oc_serial_open/read/write for agent-driven UART sessions with persisted transcripts'), which gives a clear selection rule. The inverse condition (when interactive minicom is the right choice, e.g. manual or non-persisted console work) is only implied by the contrast.

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