Skip to main content
Glama
OpenCyber Harness
by mitkox

oc_workspace_delete

Destructive

Delete a file or empty directory from an OpenCyber engagement workspace by specifying the engagement ID and path, keeping workspace contents clean and scoped.

Instructions

Delete one file or empty directory inside the OpenCyber engagement workspace.

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>",
      "path": "<path>"
    },
    "name": "oc_workspace_delete"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYes
engagement_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, idempotentHint=false and readOnlyHint=false, so the safety profile is covered structurally. The description adds a genuinely useful constraint beyond that: only empty directories can be removed, implying non-recursive behavior. It does not say whether deletion is permanent or recoverable, what happens on a non-empty directory, or whether permissions/engagement state matter, which leaves notable gaps for a destructive operation.

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?

A single front-loaded sentence with no filler; the destructive action and its target scope come first. Nothing can be trimmed without losing information.

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 annotations carry the destructive/idempotency profile. Combined with a one-sentence description of what gets deleted, the definition is close to complete, with the main remaining deficit being path format guidance rather than scope or safety.

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% for two required parameters, so the description must compensate and does not. It never explains that 'engagement_id' scopes the workspace or what form 'path' takes (relative to workspace root? absolute? file vs directory syntax), leaving the agent to guess at call format.

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 states a specific verb ('Delete') and resource ('one file or empty directory') and scopes it to the 'OpenCyber engagement workspace', which separates it from read/list/write siblings clearly enough. It stops short of naming or contrasting an alternative tool explicitly, so it is clear but not maximally differentiated.

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 is only implied: the word 'Delete' plus the 'empty directory' qualifier suggests when the tool applies, but there is no explicit statement of when to use this versus oc_workspace_write or how to clear a non-empty directory. No prerequisites, exclusions, or confirmation guidance are given.

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