Skip to main content
Glama
OpenCyber Harness
by mitkox

oc_hardware_inventory

Read-onlyIdempotent

Enumerate USB, serial, wireless, CAN, Bluetooth, video, and GPIO/I2C/SPI devices in a container plus its capabilities to map available hardware before running hardware tools.

Instructions

Enumerate hardware visible inside the container: USB devices with SDR/NFC/JTAG/serial classification, serial ports, wireless and CAN interfaces, Bluetooth adapters, video/input devices, GPIO/I2C/SPI nodes, and container capabilities. Call this before hardware tools.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "oc_hardware_inventory"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds genuine context beyond that: the scan is scoped to hardware visible *inside the container* (not the host), and it reports classification labels rather than raw dumps. It does not mention privileges/capabilities needed for the probe, but the return shape is covered by the output schema.

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?

Front-loaded with the verb and resource, followed by a single dense enumeration and a short imperative call-to-action; nothing is filler. The category list is long but each entry is meaningful for an inventory tool, so the length is justified rather than 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?

For a no-arg, read-only enumeration with a full output schema and rich annotations, what remains to explain is scope and sequencing — and both are present. The only omission is how this differs from the related plan/readiness tools, a minor gap given how self-describing the scope is.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Zero-parameter tool, so there is no parameter meaning to add and the baseline of 4 applies. The description correctly makes no attempt to describe arguments that do not exist.

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?

Opens with a specific verb-plus-resource ('Enumerate hardware visible inside the container') and then enumerates the exact categories returned (USB/SDR/NFC/JTAG, serial, wireless/CAN, Bluetooth, video/input, GPIO/I2C/SPI, capabilities), so an agent knows precisely what data this yields. It does not explicitly name or contrast with the plan/readiness siblings, which keeps it short of a 5.

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?

'Call this before hardware tools' gives a clear sequencing rule that applies to the whole hardware tool family. There is no when-not guidance and no named alternative (e.g., readiness vs. plan vs. inventory), so an agent must still infer where this stops and those begin.

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