Skip to main content
Glama
OpenCyber Harness
by mitkox

oc_testdisk

Destructive

Run forensic disk-recovery commands in an engagement workspace to inspect partitions, recover lost files, or repair filesystems using argv tokens without shell parsing.

Instructions

Run testdisk from the OpenCyber forensics toolkit. The container executes testdisk 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_testdisk"
  }
}

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/5.0
Behavior3/5

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

Annotations already disclose that the tool is destructive, non-read-only, non-idempotent, and not open-world. The description adds useful behavior beyond annotations by stating that testdisk is executed directly with argv tokens and that shell parsing is never used, plus namespace context; however, it does not explain the destructive impact or output behavior.

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?

The description is three compact sentences and front-loads the purpose. Each sentence adds some information, though the final sentence about relative paths is slightly vague and could be more precise.

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?

For a four-parameter wrapper with no schema descriptions, the description covers the required engagement_id and arguments implicitly and explains execution context. It remains incomplete on stdin semantics and detailed working-directory behavior, though the output schema means return values need not be described.

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 the description must compensate for all four parameters. It clarifies that arguments are argv tokens and hints at engagement namespace and relative working paths, but it never explains stdin or working_directory directly, leaving key optional parameters underdocumented.

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 and resource: running testdisk from the OpenCyber forensics toolkit. It is clear what the tool does, but it does not distinguish this tool from sibling forensics wrappers or explain its specific niche.

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?

The description gives operational context about engagement namespace and relative paths, but it does not say when to use this tool versus alternatives or when not to use it. An agent must infer its role from the tool name alone.

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