Skip to main content
Glama
OpenCyber Harness
by mitkox

oc_jq

Destructive

Parse, query, transform, and validate JSON and OpenAPI documents with jq in the selected engagement namespace, replacing brittle regular expressions with structured processing.

Instructions

Parse, query, transform, and validate JSON inside the selected engagement with jq. Use this instead of brittle regular expressions for JSON and OpenAPI documents. 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_jq"
  }
}

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
Behavior3/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so an agent knows this can mutate state. The description adds the execution context (engagement namespace, relative paths for artifacts), which is useful, but it never explains the potential for jq to write or overwrite files, nor what the arguments are executed against — the key risk given destructiveHint=true.

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 short sentences, front-loaded with the capability before the usage advice and execution context. Nothing is redundant, though the last two sentences are terse enough to border on underspecified.

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?

The presence of an output schema absolves the description of explaining return values, and the capability plus namespace context cover the call fundamentals. The remaining gap is the completely undocumented parameter set for a tool flagged as destructive.

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 carry the load. It only hints at working-directory semantics ('use relative paths for engagement artifacts') and says nothing about the required `arguments` array (jq argv), the `stdin` input, or the engagement scoping parameter.

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 specific verb set (parse, query, transform, validate) and resource (JSON) executed with jq, which is unambiguous. It stops short of contrasting with sibling shell-execution tools such as oc_bash, so it is clear but not fully differentiated.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

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

"Use this instead of brittle regular expressions for JSON and OpenAPI documents" gives explicit usage context and a preferred alternative technique. It does not state when not to use it (e.g., non-JSON payloads or large binary inputs), so the guidance is clear but incomplete.

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