Skip to main content
Glama
OpenCyber Harness
by mitkox

oc_picocom

Destructive

Run an interactive serial console from the selected engagement namespace for manual UART sessions, using relative paths for 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_picocom"
  }
}

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

B3.3/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, openWorldHint=true and readOnlyHint=false, so the risk profile is covered and the description rightly focuses elsewhere. It adds the namespace/relative-path scoping context, which is genuinely useful and not in the annotations. However, for an interactive console it discloses nothing about how the process is driven (how stdin is consumed, whether the call blocks, how to terminate), which is the behavior an agent most needs.

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 short sentences, front-loaded with the tool's identity, then the alternative, then the scoping rule. No redundant restatement of the title or annotations. Slightly compressed to the point of ambiguity about the console mechanics, but nothing is wasted.

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?

An output schema exists, so return values need no prose, and the safety profile is carried by annotations. What remains missing is essential for a four-parameter interactive process tool: the meaning of arguments/stdin and how a caller hands control to and exits an interactive session. Given the schema contributes zero descriptions, the description is not complete enough to invoke this reliably.

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 carries the full burden and largely fails it. Only working_directory is indirectly hinted at ('use relative paths'); engagement_id, arguments and especially stdin are never explained, and 'arguments' as a raw argv list is not clarified anywhere.

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 concrete verb+resource: an 'Interactive serial console' wrapper. It also names the sibling alternatives (oc_serial_open/read/write) for agent-driven UART work, so an agent can distinguish this from the scripted serial tools. It stops short of saying what 'interactive' concretely means in an agent context (blocking, TTY attachment), leaving the operational mode partly inferred.

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?

Gives an explicit routing rule: prefer oc_serial_open/read/write for agent-driven UART sessions with persisted transcripts, which implicitly reserves this tool for raw interactive use. It also states that execution happens in the selected engagement namespace and that engagement artifacts should use relative paths. It never states positively when this tool is the right choice, only when it is not.

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