Skip to main content
Glama
OpenCyber Harness
by mitkox

oc_lircd

Destructive

Run an IR receive/transmit daemon for LIRC-compatible hardware inside an engagement namespace, using relative paths for engagement artifacts.

Instructions

IR receive/transmit daemon for LIRC-compatible infrared hardware. 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_lircd"
  }
}

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

C2.4/5.0
Behavior2/5

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

Annotations already declare destructiveHint=true, openWorldHint=true, idempotentHint=false, covering the safety profile. The description adds only namespace context and says nothing about daemon behavior — whether it blocks, runs in the background, requires root or specific hardware, or what it does to existing IR state — which is material for a destructive daemon wrapper.

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?

Two short sentences with no filler, and the hardware-compatibility and namespace scoping constraints are front-loaded. It is efficiently written, though efficient delivery of incomplete information limits its benefit.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a destructive, open-world daemon wrapper with four undocumented parameters, the description omits argument-passing semantics, execution/blocking behavior, and prerequisites. The existing output schema covers return values, but the invocation side is under-specified for a tool of this complexity.

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 description coverage is 0% across four parameters, so the description must compensate and it largely does not. 'Use relative paths' hints at working_directory, but arguments, stdin, and engagement_id are left entirely unexplained, and there is no indication that arguments are passed verbatim to lircd.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description identifies the underlying capability as an 'IR receive/transmit daemon for LIRC-compatible infrared hardware', which is a specific resource and verb set. However, it describes the binary rather than the tool's actual interface (a command wrapper taking an arguments array, stdin, and working directory), so an agent cannot confidently tell how this differs from other oc_* command wrappers.

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 only operational guidance is 'Runs from the selected engagement namespace; use relative paths for engagement artifacts', which is path scoping, not when-to-use guidance. There is no mention of when to choose this over any alternative or what preconditions exist for invoking lircd.

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