Skip to main content
Glama
OpenCyber Harness
by mitkox

oc_urjtag

Destructive

Detect and interact with JTAG chains through UrJTAG, running inside the engagement namespace and using relative paths for artifacts.

Instructions

Detect and interact with JTAG chains through UrJTAG. 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_urjtag"
  }
}

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

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

The annotations already declare destructiveHint=true, openWorldHint=true, non-idempotent and non-read-only, so the safety profile is carried by structured data. The description usefully adds that execution is scoped to the engagement namespace and that artifact paths should be relative (affecting where side effects land), but it never explains that the tool is a passthrough to arbitrary UrJTAG arguments or what state changes/'interact' can cause.

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, front-loaded with the core purpose and followed by operational scoping advice; nothing is redundant. It is arguably over-terse for a destructive CLI wrapper, but as structure and economy go it is clean.

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?

An output schema exists, so return values need no explanation, but for a destructive, open-world tool with four undocumented parameters (0% coverage) the description leaves the agent unable to know how to construct 'arguments', how stdin is used, or what 'interact' entails. The namespace/relative-path note is the only operational detail provided.

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%, so the description must compensate and does not: the four parameters (engagement_id, arguments, stdin, working_directory) are never explained. Only 'use relative paths' indirectly hints at working_directory semantics; the critical 'arguments' array is left completely unspecified as to format or ordering.

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 ('Detect and interact with') and resource ('JTAG chains') plus the underlying utility (UrJTAG), so an agent can tell it is a hardware/JTAG interface rather than a generic shell. It does not name any sibling or contrast itself with the shell/binary-analysis tools in the catalog, which keeps it just 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 Guidelines3/5

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

'Detect and interact with JTAG chains' implies the context (hardware debugging/flashing work), and the second sentence tells the agent it must run inside the selected engagement namespace with relative paths. There is no explicit when-to-use, when-not-to-use, or alternative tool named, so guidance is implied rather than stated.

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