Skip to main content
Glama
OpenCyber Harness
by mitkox

oc_hardware_plan

Read-onlyIdempotent

Generates a deterministic physical-layer playbook for domains like USB, SDR, Wi-Fi, Bluetooth, NFC, JTAG, serial, automotive, logic, GPS, IR and firmware, listing prerequisite steps and catalog tool names to plan an authorized engagement.

Instructions

Return a deterministic physical-layer playbook (usb, sdr, wifi, bluetooth, nfc, jtag, serial, automotive, logic, gps, ir, firmware) using catalog tool names and prerequisites.

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": {
      "domain": "<domain>"
    },
    "name": "oc_hardware_plan"
  }
}

Input Schema

NameRequiredDescriptionDefault
domainYes
targetNo
objectiveNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so 'deterministic' largely restates idempotentHint. The one genuinely additive piece is 'using catalog tool names and prerequisites', which tells the agent the playbook is composed from other tools rather than free-form prose. Nothing is said about failure modes, unknown domains, or authorization needs.

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?

A single front-loaded sentence: verb, resource, key behavioral modifier, then the domain list. The parenthetical enumeration is long but every item earns its place as the de facto domain enum. No filler clauses or restated title.

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 the description need not describe the returned playbook structure, and annotations cover the safety profile. The remaining gap is guidance on target/objective and on sibling selection, which is a real but bounded omission for a three-parameter planning tool.

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 does supply the valid values for the required 'domain' parameter (usb, sdr, wifi, bluetooth, nfc, jtag, serial, automotive, logic, gps, ir, firmware), which is valuable since the schema defines no enum. However, 'target' and 'objective' are never explained, leaving two of three parameters undocumented in both schema and description.

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 names a concrete verb and resource ('Return a deterministic physical-layer playbook') and enumerates the twelve covered domains in parentheses, so the agent immediately knows the scope. It does not explicitly distinguish itself from hardware-related siblings such as oc_hardware_readiness or oc_hardware_inventory, 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 Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use / when-not-to-use statement and no reference to any alternative. An agent facing oc_hardware_readiness, oc_hardware_inventory, or oc_chain_plan gets no signal about which one produces a plan versus a status or inventory. The domain enumeration hints at applicability but only implicitly.

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