Skip to main content
Glama
OpenCyber Harness
by mitkox

oc_strings

Destructive

Extract printable strings from binaries and engagement artifacts by running the strings utility with exact argv tokens inside an isolated engagement workspace, without shell parsing.

Instructions

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

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

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

With annotations already declaring destructiveHint=true and openWorldHint=false, the description still adds real behavioral context: direct exec with argv tokens and no shell parsing (a meaningful injection-safety detail), plus namespace scoping and relative-path expectations. It does not explain why a read-only `strings` invocation is flagged destructive, leaving that annotation unexplained.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three tight sentences, each carrying distinct information: what runs, how it executes, and the filesystem/namespace convention. Nothing is redundant and the identification is front-loaded.

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?

An output schema exists, so return values need not be described, and the execution model and path convention are covered. The remaining gaps are the undocumented `stdin` input and the working_directory default, minor for a thin binary wrapper but not zero.

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 carry the load; it partially does by framing 'arguments' as argv tokens, implying engagement scoping for engagement_id, and hinting at working_directory via relative paths. The `stdin` parameter and defaults are never addressed, so the compensation is incomplete.

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 and resource ('Run strings from the OpenCyber binary toolkit'), which is enough to distinguish it from generic siblings like oc_bash. It does not explicitly compare itself to any named alternative, so it stops 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?

Usage context is only implied: 'Runs from the selected engagement namespace; use relative paths for engagement artifacts' gives an operating convention but never states when to pick this tool over oc_bash or oc_binwalk. No exclusions or prerequisites are mentioned.

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