Skip to main content
Glama
OpenCyber Harness
by mitkox

oc_hardware_readiness

Read-onlyIdempotent

Reports hardware readiness by domain (SDR, Wi-Fi, Bluetooth, NFC, JTAG, serial, CAN, logic, GPS, IR) and returns host Docker flags for exposing missing devices, separate from tool installs.

Instructions

Report per-domain hardware readiness (SDR, Wi-Fi, Bluetooth, NFC, JTAG, serial, CAN, logic, GPS, IR) with the host docker flags needed to expose missing devices. Separate from tool installation readiness.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so safety needs no restatement. The description adds real behavioral context beyond them: the output is per-domain readiness plus the host docker flags required to expose missing devices, which tells the agent the report is actionable rather than merely diagnostic.

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 sentences, both front-loaded with the highest-value information: first what is reported and for which domains, then the scope boundary. There is no filler, restatement of the title, or hedging language.

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?

With no parameters and an output schema present, the definition only needs to establish scope and what the report contains, both of which it does. The only gap is that it never points the agent at the complementary inventory or plan tools when readiness fails.

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?

The tool takes zero parameters, so the schema imposes no semantic burden and the baseline of 4 applies. The description correctly adds nothing about inputs and instead spends its words on scope and output content.

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 definition pairs a specific verb ("Report") with a specific resource ("per-domain hardware readiness") and enumerates the exact domains checked (SDR, Wi-Fi, Bluetooth, NFC, JTAG, serial, CAN, logic, GPS, IR), so an agent knows precisely what it returns. It does not name the closest siblings (oc_hardware_inventory, oc_hardware_plan), so sibling differentiation is implied rather than explicit.

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?

"Separate from tool installation readiness" gives one useful exclusion, telling the agent this is not the software-readiness check. However, there is no positive when-to-use trigger and no named alternative for the installation-readiness case, leaving the agent to infer routing from a negative clause alone.

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