Skip to main content
Glama
OpenCyber Harness
by mitkox

oc_netbios_scan

Destructive

Execute NetBIOS scans with nbtscan to enumerate Windows hosts and shares in an engagement workspace, using safe argv tokens without shell parsing.

Instructions

Run netbios scan from the OpenCyber network toolkit. The container executes nbtscan directly with the supplied argv tokens; shell parsing is never used. 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_netbios_scan"
  }
}

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

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

The annotations already flag the operation as destructive, open-world, and non-idempotent, so the description does not need to repeat that. It adds useful behavior beyond annotations: the container executes `nbtscan` directly with argv tokens, shell parsing is never used, and execution occurs within the engagement namespace with relative paths for artifacts.

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?

The description is three sentences, front-loads the purpose, and then adds execution and path semantics. Every sentence contributes useful information without repetition.

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?

The tool is a destructive open-world scan runner with four parameters and no schema descriptions, and an output schema exists. The description covers the execution model and path behavior, but it does not fully explain the parameters or the practical implications of the destructive annotation, leaving meaningful gaps.

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%, so the description must carry parameter meaning. It clarifies that `arguments` are raw argv tokens passed directly to `nbtscan` and that the engagement namespace affects execution, but it leaves `stdin`, `working_directory`, and argument formatting without explicit explanation.

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: running a netbios scan using `nbtscan` from the OpenCyber toolkit. It is clear enough to distinguish from unrelated tools, but it does not explicitly differentiate this scan from sibling network scanners such as `oc_arp_scan` or `oc_pcsc_scan`.

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 contextual guidance about running from the selected engagement namespace and using relative paths for engagement artifacts. However, it does not say when to prefer this tool over other scan tools, nor does it state any preconditions or exclusions.

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