Skip to main content
Glama
OpenCyber Harness
by mitkox

oc_rtl_test

Destructive

Executes rtl_test via direct argv tokens inside a selected engagement namespace, avoiding shell parsing and supporting relative paths for engagement artifacts.

Instructions

Run rtl test from the OpenCyber rf toolkit. The container executes rtl_test 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_rtl_test"
  }
}

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

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

Beyond the annotations, the description discloses important execution behavior: the container invokes rtl_test directly with supplied argv tokens and never uses shell parsing. It also notes engagement-namespace execution and relative-path handling. It stops short of explaining what the destructiveHint=true behavior actually affects, but it adds meaningful invocation context not present in the annotations.

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 tight sentences with the purpose front-loaded, followed by execution and path semantics. Every sentence contributes relevant information and there is no redundant wording.

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?

For a destructive, open-world tool with four parameters and no schema descriptions, the description covers the core execution model and path conventions. It still omits stdin semantics and does not clarify the nature of the destructive behavior, but the presence of an output schema reduces the need to explain return values.

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 compensate. It clarifies that arguments are directly passed argv tokens, that execution occurs in the selected engagement namespace, and that working_directory should use relative paths. However, it does not mention the optional stdin parameter or give argument-format details, so compensation is only partial.

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 uses a specific verb and resource: 'Run rtl test from the OpenCyber rf toolkit.' This clearly identifies the operation as executing the rtl_test utility, but it does not differentiate the tool from RF siblings such as oc_rtl_433, oc_rtl_power, or oc_rtl_sdr.

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?

The description supplies operational context such as running from the selected engagement namespace and using relative paths, but it gives no guidance on when to choose this tool over its RF siblings, nor does it state prerequisites, exclusions, or typical use cases.

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