Skip to main content
Glama
OpenCyber Harness
by mitkox

oc_gdb

Destructive

Execute GDB debugging sessions within a selected engagement workspace to inspect and control binaries, passing explicit argument tokens without shell parsing.

Instructions

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

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, readOnlyHint=false and openWorldHint=false, so the safety profile is covered. The description goes beyond them by disclosing that shell parsing is never used -- a material fact for an agent building argv tokens and expecting no metacharacter expansion -- plus the namespace scoping and relative-path convention. It stops short of saying what state a destructive run affects.

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 with the core action front-loaded and no filler; the no-shell-parsing note follows logically. Nothing is redundant, though the namespace and relative-path clauses could be merged into one tighter sentence.

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 annotations carry the risk profile. Still, for a destructive four-parameter tool at 0% schema coverage, the omission of stdin semantics leaves a real gap an agent must guess at.

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% for four parameters, so the description must compensate and only partly does: "supplied argv tokens" maps to arguments, "selected engagement namespace" to engagement_id, and "relative paths" to working_directory. The stdin parameter is never mentioned, and no format or sizing expectations are given for arguments.

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?

"Run gdb from the OpenCyber binary toolkit" states a specific verb and resource, and "container executes gdb directly with the supplied argv tokens" pins down the execution model. It does not distinguish itself from the sibling oc_gdb_multiarch, so an agent must infer which gdb variant to pick.

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?

The line "Runs from the selected engagement namespace; use relative paths for engagement artifacts" gives useful operating context, but there is no explicit when-to-use or when-not-to-use guidance and no routing to oc_gdb_multiarch or to shell-based alternatives like oc_bash. Usage 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