Skip to main content
Glama
OpenCyber Harness
by mitkox

oc_serial_write

Destructive

Writes text or hexadecimal bytes to a live serial session, capped at 65,536 bytes per call and saved in the transcript.

Instructions

Write text or hexadecimal bytes to a live serial session. Writes are limited to 65536 bytes per call and persisted in the transcript.

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>",
      "session_id": "<session_id>"
    },
    "name": "oc_serial_write"
  }
}

Input Schema

NameRequiredDescriptionDefault
dataNo
hex_dataNo
session_idYes
engagement_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already flag this as destructive and non-idempotent, so safety is covered. The description adds genuinely new behavioral facts: a 65536-byte per-call limit and that writes are persisted in the transcript, both of which affect how an agent should batch data and reason about audit trails.

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?

Two tight sentences with the action and its constraints front-loaded. Nothing is redundant or padded.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/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 needn't be explained, and the description covers the core behavior plus size and persistence constraints. The remaining gap is how data vs hex_data should be supplied, which for a 0%-coverage schema is a noticeable but not fatal omission.

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 coverage is 0% across four parameters, so the description carries the full burden. It clarifies that data can be plain text or hex bytes, but it never explains the relationship between data and hex_data (mutual exclusivity, precedence, defaults) nor what engagement_id and session_id refer to.

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 ("Write text or hexadecimal bytes to a live serial session"), which clearly separates it from oc_serial_read and oc_serial_close. It's clear, though it doesn't name or contrast with any sibling explicitly.

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 phrase "live serial session" implies a session must already be open, which is useful context, but there is no explicit when-to-use guidance or mention of alternatives such as oc_serial_open or oc_workspace_write. Usage is only weakly implied.

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