Skip to main content
Glama
OpenCyber Harness
by mitkox

oc_rtl_433

Destructive

Decode sub-GHz 433/315/868/915 MHz sensor and remote-control protocols to identify wireless devices during physical security assessments, running from an engagement workspace.

Instructions

Decode 433/315/868/915 MHz sensor and remote-control protocols with rtl_433. Common first step for sub-GHz physical security assessments. 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_433"
  }
}

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

B3.2/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, openWorldHint=true, and non-idempotent, so the safety profile is carried by structured data. The description adds useful behavioral context about the engagement namespace and relative artifact paths, but it never discloses what 'destructive' actually means here or what side effects to expect from a decode operation.

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?

Three tight sentences with the purpose front-loaded, followed by usage positioning and working-directory guidance. No filler, though the namespace/path sentence could be slightly more precise about which parameter it maps to.

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?

An output schema exists, so return values needn't be described. But for a tool whose main inputs are raw CLI arguments with 0% schema coverage, the description leaves the agent guessing how to populate 'arguments' and 'stdin,' making it only adequate.

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

Parameters2/5

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

Schema coverage is 0% for four parameters, so the description must compensate and largely does not. It hints at working_directory/engagement_id via 'relative paths for engagement artifacts,' but the arguments and stdin parameters (the core rtl_433 CLI pass-through) are left entirely unexplained.

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?

States a specific verb (Decode) and resource (433/315/868/915 MHz sensor and remote-control protocols via rtl_433), so the agent knows exactly what the tool does. It positions itself as a 'first step' in sub-GHz work but doesn't explicitly name the neighboring rtl_power/rtl_sdr tools to differentiate.

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 phrase 'Common first step for sub-GHz physical security assessments' gives implied usage context, which helps an agent decide when this is appropriate. However, there are no explicit when-not conditions, prerequisites, or named alternatives such as rtl_power for spectrum scanning.

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