Skip to main content
Glama

dd

Destructive

Copy and convert data blocks between files with block-level precision. Supports preview and dry-run to avoid unintended overwrites.

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
bsNoBlock size in bytes.
rawNoWrite selected input bytes without a JSON envelope.
convNoComma-separated conversions: notrunc, noerror, fsync, sync.
seekNoOutput blocks to seek before writing.
skipNoInput blocks to skip.
countNoNumber of input blocks to copy.
inputNoInput file, or '-' for stdin.-
outputNoOutput file, or '-' for stdout/no file output.-
dry_runNoReport without writing output.
parentsNoCreate missing output parent directories.
operandsNoGNU-style key=value operands (if=, of=, bs=, count=, ...).
allow_overwriteNoAllow replacing an existing output file.
max_preview_bytesNoMaximum JSON preview bytes.
Behavior4/5

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

Description aligns with annotations (destructiveHint: true) by noting 'Destructive to output'. Adds context beyond annotations: mentions dry-run, returns JSON with throughput, and block-level behavior.

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?

Description is concise with 4 sentences, front-loads core purpose, and every sentence adds value. No redundant 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?

Given the tool complexity (13 params, no output schema), the description covers purpose, usage guidance, return format, and behavioral expectations. Could briefly mention conversion options but schema covers them.

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 description coverage is 100%, so baseline is 3. Description does not add substantial parameter-level detail beyond schema, but mentions '--dry_run' and 'bounded preview' which provide minor additional context.

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 between input and output, adding 'bounded preview and dry-run support' for specificity. It distinguishes from sibling 'cp' by noting it is for block-level copying, not simple file copying.

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 data copying and format conversion) and when not to use (simple file copying, refer to 'cp'). Provides alternatives: 'cp' and 'truncate'.

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