Skip to main content
Glama
OpenCyber Harness
by mitkox

oc_gdb_multiarch

Destructive

Debug ARM, MIPS, and other foreign-architecture firmware with GDB inside an engagement namespace, using relative paths to reference engagement artifacts.

Instructions

Debug ARM, MIPS, and other foreign-architecture firmware with GDB. 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_gdb_multiarch"
  }
}

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?

Annotations already declare destructiveHint=true, openWorldHint=true, non-idempotent and non-read-only, so the risk profile is partly conveyed structurally. The description adds useful operational context about namespace scoping and relative artifact paths, but says nothing about the fact that this runs an interactive debugger over untrusted binaries, whether stdin feeds the debugger session, or any timeout/termination behavior — material for a destructive, open-world tool.

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 tight sentences with the capability statement front-loaded and the environment constraint second. Nothing is wasted, though the brevity comes at the cost of the missing parameter detail rather than being efficient compression.

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 not be described. However, for a destructive, open-world tool that takes a free-form argument array and stdin, the definition leaves an agent without enough to call it correctly — how 'arguments' is composed, what stdin does, and how the debugger session terminates are all unaddressed.

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 carry parameter meaning and largely does not. It only gestures at engagement_id (engagement namespace) and working_directory (relative paths); the required 'arguments' array, which plainly holds the GDB invocation arguments, and the 'stdin' parameter are never explained in the description or the schema.

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 concrete verb (Debug) and a concrete resource (ARM, MIPS, and other foreign-architecture firmware with GDB), which is far more specific than the bare tool name. It implicitly separates itself from the sibling oc_gdb by scoping to foreign-architecture targets, though it never names that sibling, so the differentiation is inferential rather than explicit.

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?

'Debug ARM, MIPS, and other foreign-architecture firmware' implies the selection condition, and the second sentence gives a usage constraint (runs from the selected engagement namespace, use relative paths). What is missing is explicit guidance on when to prefer this over the plain oc_gdb sibling, and there are no stated prerequisites or exclusions.

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