Skip to main content
Glama
OpenCyber Harness
by mitkox

oc_radare2

Destructive

Run radare2 binary analysis commands from an engagement workspace using direct argv tokens, so reverse-engineering tasks avoid shell parsing and use relative artifact paths.

Instructions

Run radare2 from the OpenCyber binary toolkit. The container executes radare2 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_radare2"
  }
}

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

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the safety profile is known. The description adds genuinely new behavioral context: execution happens inside the container without shell parsing (so argv tokens are passed literally, not interpreted), and execution is scoped to an engagement namespace. It does not say what the tool may modify on disk or how timeouts/exit codes behave, which keeps it from a 5.

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 core action and followed by the two execution constraints that matter most. No filler, though the namespace sentence is slightly compressed and could state its consequence more directly.

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 need no explanation, and the description covers the execution model and path scoping. For a destructive arbitrary-binary runner, though, it omits stdin handling, working-directory semantics relative to the namespace, and any note about side effects on engagement artifacts.

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 for four undocumented parameters. It gives partial meaning: 'arguments' are argv tokens passed without shell parsing, and the engagement namespace plus 'relative paths' hint at engagement_id and working_directory. The 'stdin' parameter is never mentioned, leaving a real gap.

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 executable ('radare2') and states exactly how it is invoked ('directly with the supplied argv tokens'), which lets an agent distinguish this from general-purpose siblings like oc_bash. It stops short of pointing at an explicit alternative for binary analysis, so it is clear but not sibling-differentiating.

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?

There is implied guidance: it runs from the selected engagement namespace and artifacts should be referenced with relative paths. However, it never says when to prefer this over oc_bash or another binary tool, and gives no preconditions such as required engagement context or expected invocation syntax.

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