Skip to main content
Glama
OpenCyber Harness
by mitkox

oc_anew

Destructive

Append only new lines from supplied stdin to an engagement artifact, preventing duplicate entries during authorized security data collection.

Instructions

Run anew from the OpenCyber web toolkit. The container executes anew 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_anew"
  }
}

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
Behavior4/5

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

Annotations already declare destructiveHint=true, readOnlyHint=false, openWorldHint=true and idempotentHint=false, so the safety profile is covered. The description adds genuinely non-obvious behavior: arguments are passed as raw argv tokens with no shell interpretation (so no pipes, redirects, or globbing), and execution is scoped to the engagement namespace rooted at the working directory. It still omits how the `stdin` parameter interacts with the process and what the tool does to files on disk.

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 execution model front-loaded and no filler; each sentence adds a distinct fact. Slight loss for spending words on restating the toolkit name instead of describing the binary's function.

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 not be explained, and the annotations cover safety. What remains missing is the core functional description of `anew` and the role of `stdin`, which matters for a destructive, open-world executor with fully undocumented parameters.

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?

With 0% schema description coverage, the description must carry parameter meaning. It does clarify that `arguments` are discrete argv tokens (not a shell string) and that `working_directory` should hold relative engagement artifact paths under the engagement namespace implied by `engagement_id`. The `stdin` parameter is never mentioned, leaving one of four parameters undocumented in both schema and prose.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description gives a specific verb ('Run anew') and identifies the binary and its host ('OpenCyber web toolkit'), which distinguishes it from unrelated siblings. However, it never explains what the `anew` utility actually does (e.g., appending only new lines to a file), so an agent that doesn't already know the binary cannot reason about its effect; it only knows that a named binary is executed.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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

There is no guidance on when to choose this over the generic `oc_bash` or other siblings, and no prerequisites or exclusions are stated. The only usage-flavored material is the instruction to use relative paths within the engagement namespace and that shell parsing is not used, which is operational context rather than tool-selection guidance.

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