Skip to main content
Glama
OpenCyber Harness
by mitkox

oc_workspace_write

Destructive

Write or append a UTF-8 text file inside an OpenCyber engagement workspace, letting you save notes, findings, or logs to a scoped engagement path.

Instructions

Write or append a UTF-8 text file 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>",
      "content": "<content>"
    },
    "name": "oc_workspace_write"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYes
appendNo
contentYes
engagement_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.7/5.0
Behavior2/5

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

Annotations already declare destructiveHint=true, readOnlyHint=false, and idempotentHint=false, but the description adds almost no behavioral context beyond 'UTF-8 text'. It never states that the default mode overwrites an existing file (the most consequential behavior), whether parent directories are created, how path traversal is restricted, or what happens on failure, so an agent must guess at the riskiest semantics.

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?

A single front-loaded sentence with no filler or repetition. However, the brevity comes at the cost of the missing semantics rather than being efficiently dense, so it is not a 5.

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 explained, but for a destructive write tool with 0% parameter documentation the description leaves critical gaps: overwrite behavior, path resolution, and engagement scoping. An agent could call it and silently destroy an existing file without the description warning it.

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 all four parameters (engagement_id, path, content, append) are undocumented in structured data. The description only weakly hints at 'content' being UTF-8 text and at an append mode, saying nothing about engagement_id scoping, path format (absolute vs relative), or how append interacts with existing files.

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 gives a concrete verb (write or append), a concrete resource (UTF-8 text file), and a scoping constraint (inside the OpenCyber engagement workspace), which distinguishes it from tools like oc_serial_write or oc_workspace_read. It does not explicitly name a sibling to differentiate from, which keeps it below 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 Guidelines2/5

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

There is no explicit guidance on when to use this versus oc_workspace_read, oc_workspace_delete, or oc_serial_write, and no mention of prerequisites such as the engagement existing or the path being workspace-relative. The only implied usage signal is the word 'workspace', leaving the agent to infer conditions.

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