Skip to main content
Glama

dd

Destructive

Copy and convert data blocks between files with dry-run preview. Destructive writes; returns JSON of bytes and throughput.

Instructions

Copy and convert data blocks between input and output with bounded preview and dry-run support. Destructive to output: writes data to the destination file. Use --dry_run to preview the operation. Returns JSON with bytes read/written and throughput. Use for block-level data copying and format conversion. Not for simple file copying — use 'cp' for files and directories. See also 'cp', 'truncate'.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
allow_overwriteNoAllow replacing an existing output file.
bsNoBlock size in bytes.
countNoNumber of input blocks to copy.
dry_runNoReport without writing output.
inputNoInput file, or '-' for stdin.-
max_preview_bytesNoMaximum JSON preview bytes.
outputNoOutput file, or '-' for stdout/no file output.-
parentsNoCreate missing output parent directories.
rawNoWrite selected input bytes without a JSON envelope.
seekNoOutput blocks to seek before writing.
skipNoInput blocks to skip.
Behavior4/5

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

Annotations already indicate destructiveHint=true. Description reinforces destructive nature and adds details: returns JSON with bytes and throughput. Provides safety context with dry-run option.

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?

Five sentences, front-loaded with purpose, then destructive warning, dry-run, output format, and usage context. No redundancy.

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?

Given 11 parameters and no output schema, description covers key behavioral aspects (destructive, dry-run, JSON output) and usage context. Schema covers parameter details, so description is adequately complete.

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 coverage is 100%, so baseline is 3. Description mentions --dry_run and preview but does not add significant meaning beyond schema descriptions for other parameters.

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

Purpose5/5

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

The description clearly states the tool copies and converts data blocks, with specific verb and resource. It distinguishes from sibling tools like 'cp' for simple file copying and references 'truncate'.

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

Usage Guidelines5/5

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

Explicitly states when to use (block-level copying, format conversion) and when not to (use 'cp' for files/directories). Mentions dry-run for preview and references alternatives.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/caseSHY/AI-CLI'

If you have feedback or need assistance with the MCP directory API, please join our Discord server