Skip to main content
Glama
OpenCyber Harness
by mitkox

oc_serial_close

Close a live serial session to restore terminal attributes and return the transcript path, ensuring clean teardown after device or console work.

Instructions

Close a live serial session, restore terminal attributes, and return the transcript path.

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_close"
  }
}

Input Schema

NameRequiredDescriptionDefault
session_idYes
engagement_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=false, openWorldHint=false, so the safety profile is covered. The description still earns credit by disclosing behavior not in annotations: it restores terminal attributes (a real system side effect) and yields a transcript path. It stops short of saying what happens on an already-closed or unknown session_id, which matters given idempotentHint=false.

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?

A single front-loaded sentence that packs purpose, side effect, and return value with zero filler. Every clause carries information an agent would otherwise have to guess.

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 the return value need not be spelled out further, and the safety profile is carried by annotations. The remaining gap is parameter meaning for a required two-parameter teardown call, which leaves the definition only minimally sufficient.

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% and both parameters are required, yet the description never mentions engagement_id or session_id, nor their relationship (e.g., whether session_id is unique per engagement or globally). With low coverage the description should compensate and it does not.

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 gives a specific verb and resource ('Close a live serial session') plus two concrete side effects (restoring terminal attributes, returning the transcript path). This clearly distinguishes it from oc_serial_open/read/write by name semantics alone, though it never explicitly names a sibling or states scope boundaries.

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 explicit when-to-use guidance, no prerequisites, and no mention of alternatives such as oc_serial_list or what to do if the session is already gone. The phrase 'live serial session' weakly implies it is the teardown step after open/read/write, but the agent must infer that ordering.

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